Menu

#6559 Pickup and use eventual HTTP proxy

open
nobody
2019-03-15
2019-03-08
Anonymous
No

Originally created by: joakimr-axis

Without passing proper proxy settings to the docker build command, it
will fail. This patch mitigates that (and works if no proxy is set).

Change-Id: I81e50b173047dd4a92b5a38a4940eff3453c8b80
Signed-off-by: Joakim Roubert joakimr@axis.com

Resolves [#2590]

Discussion

  • Anonymous

    Anonymous - 2019-03-08

    Originally posted by: joakimr-axis

    How should I interpret this output from Jenkins?

    10:33:49 b6da999fed9c: Retrying in 2 seconds
    10:33:50 b6da999fed9c: Retrying in 1 second
    10:33:59 efa807d0493e: Pushed
    10:33:59 received unexpected HTTP status: 500 Internal Server Error
    [Pipeline] }
    [Pipeline] // stage
    [Pipeline] }
    [Pipeline] // wrap
    [Pipeline] }
    [Pipeline] // wrap
    [Pipeline] }
    [Pipeline] // withDockerRegistry
    [Pipeline] }
    [Pipeline] // node
    [Pipeline] End of Pipeline
    
    GitHub has been notified of this commits build result
    
    ERROR: script returned exit code 1
    Finished: FAILURE
    

    Internal error, why? Something I can do about it, and if so, how?

     
  • Anonymous

    Anonymous - 2019-03-08

    Originally posted by: ijc

    The 500 is an external issue, the appropriate people have been paged.

    Sorry for the inconvenience.

     
  • Anonymous

    Anonymous - 2019-03-11

    Originally posted by: GordonTheTurtle

    Please sign your commits following these rules:
    https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
    The easiest way to do this is to amend the last commit:

    $ git clone -b "httpproxy" git@github.com:joakimr-axis/compose.git somewhere
    $ cd somewhere
    $ git rebase -i HEAD~842357815536
    editor opens
    change each 'pick' to 'edit'
    save the file and quit
    $ git commit --amend -s --no-edit
    $ git rebase --continue # and repeat the amend for each commit
    $ git push -f
    

    Amending updates the existing PR. You DO NOT need to open a new one.

     

Log in to post a comment.