-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add command line flag for overriding plugin info location + document proxy configuration #106
Conversation
The URL to plugin-versions.json is hard-coded unlike all other URLs. This commit also updates the readme to provide guidance for people in a highly locked down corporate environment.
In addition to being easier for everyone this is particularly helpful behind a corporate proxy where connecting to the non-standard maven repository https://repo.jenkins-ci.org/public/ can be challenging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One issue about http
README.md
Outdated
#### Proxy Support | ||
Proxy support is available using standard [Java networking system properties](https://docs.oracle.com/javase/7/docs/api/java/net/doc-files/net-properties.html) `http.proxyHost` and `http.proxyPort`. Note that this provides only basic NTLM support and you may need to use an authentication proxy like [CNTLM](https://sourceforge.net/projects/cntlm/). | ||
|
||
If you are behind a corporate proxy using a self-signed certificate you may wish to use the http variants of the default urls. The full list is given below for convenience. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t think recommending http is a good idea, it’ll likely break at some point when https in enforced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, thanks for the pull request!
Thanks for the tool. We too have created something similar and I would like to delete ours and use this instead. I have only just started experimenting, this PR contains what I needed in terms of code patches and some documentation that would have shaved hours off the time it took me to work this all out.
In summary:
DEFAULT_PLUGIN_INFO_LOCATION
to be overridden via cli and env like the other URLs.