<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I've been looking into how to push git changes back to SLAC and
have found a path, but it takes a few hops.</p>
<p>Problem 1. We can't get an AFS token from jlabl1, so we can't
push directly to SLAC and need to go through an external git repo
such as github.</p>
<p>Problem 2. We can't connect to github from lclsapp1.</p>
<p>From jlabl1 we can push to github by adding our jlabl1 ssh key to
our github account.</p>
<p>And I can push from lclsapp1 to jlabl1 by creating another tunnel
w/ a new port number from localhost to jlabl1.</p>
<p>So the path is:</p>
<ol>
<li>push from lclsapp1 to a git repo you've already created on
jlabl1.</li>
<li>ssh to jlabl1 and push to github.</li>
<li>From SLAC, pull changes from github.</li>
</ol>
<p>I think we can probably use a variant of the
/usr/local/bin/git-ssh wrapper script to run a proxycmd on jlabl1
which would allow us to push to github from lclsapp1, but that'll
take more work to figure out.</p>
<p>My test cases were:</p>
<p>lclsapp1:/usr/local/lcls/epics/setup</p>
<p>jllabl1:/u/home/bhill/git-wa/setup/epics-setup-git<br>
</p>
<p>Cheers,</p>
<p>- Bruce</p>
<p>P.S. I set GIT_COMMITTER_EMAIL and GIT_AUTHOR_EMAIL in
~softegr/setup/git-setup.bash so we'll get proper email addr in
our git logs. You can also customize GIT_AUTHOR_NAME and
GIT_COMMITTER_NAME in your ~/$SOFTEGR_USER/ENVS file.q<br>
</p>
<pre class="moz-signature" cols="120">--
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA 94025
</pre>
</body>
</html>