Use proxy configuration when connecting to CloudFoundry#3
Closed
buchen wants to merge 2 commits intojenkinsci:masterfrom
buchen:feature_auto_proxy_cfg
Closed
Use proxy configuration when connecting to CloudFoundry#3buchen wants to merge 2 commits intojenkinsci:masterfrom buchen:feature_auto_proxy_cfg
buchen wants to merge 2 commits intojenkinsci:masterfrom
buchen:feature_auto_proxy_cfg
Conversation
Member
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
Author
|
As discussed here https://issues.jenkins-ci.org/browse/JENKINS-26598 |
|
Thanks again! This will be included in v1.2 which should be released relatively soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of requiring an explicit configuration of the proxy, this change uses the configured proxies by the Java Virtual Machine.
This change will not use the proxy configuration which is done in "configure jenkins" -> "manage plug-ins" -> "advanced". To me, that seems to be specific to the update mechanism.
Feel free to use.