[Lerftest-ctrls] Pushing changes back to SLAC

[Wesley Moore]

Github was discussed in conversations previously.  HTTP/HTTPS can be routed through the proxy.  SSH is blocked to remote sites for security.   So use the url to push from any host.  




Prevents an internal, comprised host from shipping data off to any remote server.  




Wesley






On Sat, May 12, 2018 at 3:58 AM -0400, "Bruce Hill" <bhill at slac.stanford.edu> wrote:











  

    
  
  
    

I've been looking into how to push git changes back to SLAC and
      have found a path, but it takes a few hops.
    

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.
    

Problem 2.  We can't connect to github from lclsapp1.
    

>From jlabl1 we can push to github by adding our jlabl1 ssh key to
      our github account.
    

And I can push from lclsapp1 to jlabl1 by creating another tunnel
      w/ a new port number from localhost to jlabl1.
    

So the path is:
    
      push from lclsapp1 to a git repo you've already created on
        jlabl1.
      ssh to jlabl1 and push to github.
      From SLAC, pull changes from github.
    
    

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.
    

My test cases were:
    

lclsapp1:/usr/local/lcls/epics/setup
    

jllabl1:/u/home/bhill/git-wa/setup/epics-setup-git

    
    

Cheers,
    

- Bruce
    

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

    
    -- 
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA  94025

  






I've been looking into how to push git changes back to SLAC and have found a path, but it takes a few hops.

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.

Problem 2.  We can't connect to github from lclsapp1.

 From jlabl1 we can push to github by adding our jlabl1 ssh key to our github account.

And I can push from lclsapp1 to jlabl1 by creating another tunnel w/ a new port number from localhost to jlabl1.

So the path is:

 1. push from lclsapp1 to a git repo you've already created on jlabl1.
 2. ssh to jlabl1 and push to github.
 3.  From SLAC, pull changes from github.

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.

My test cases were:

lclsapp1:/usr/local/lcls/epics/setup

jllabl1:/u/home/bhill/git-wa/setup/epics-setup-git

Cheers,

- Bruce

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

-- 
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA  94025

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/lerftest-ctrls/attachments/20180512/9ad5b05c/attachment.html>
-------------- next part --------------
_______________________________________________
Mailing List: Lerftest-ctrls at jlab.org
https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
Wiki: https://wiki.jlab.org/lerf/index.php/Network