The wiki edits look good to me. If the proxy config is indeed global it seems to be located in the wrong spot in the UI. Probably a historic thing that should be fixed in 2.0.
I would apply those changes and move on. Manfred On Wed, Feb 24, 2016 at 9:47 AM, Olivier Dagenais < [email protected]> wrote: > Hi, > > I'm nearing the end of verifying proxy support for the Jenkins TFS plugin > <https://github.com/jenkinsci/tfs-plugin> and I thought I would update > the proxy documentation in the Jenkins wiki > <https://wiki.jenkins-ci.org/display/JENKINS/JenkinsBehindProxy>, so I > could point my users to it. See jenkins pull request #2060 > <https://github.com/jenkinsci/jenkins/pull/2060> for a related change. > > Since Confluence doesn't have a pull request system for reviewing edits to > pages, I figured posting to this mailing list was the next best thing. (we > solved this problem by moving most of our wiki page contents to our > README.md in GitHub) > > > I am attaching version 4 of the JenkinsBehindProxy page as well as my > proposed edits, including the example configuration screenshot. I removed > the empty sections and replaced the "How Jenkins handles Proxy Servers" > with what seems to be the case, at least in my testing and casual scanning > of the source code. > > Some questions I have: > > 1. Is this the right guidance for deploying Jenkins behind a proxy? > In other words, is the statement "*This is preferred over setting JVM > properties.*" (referring to using the HTTP Proxy Configuration) > accurate? Do we know of things that break if users behind a proxy server > stop using the JVM properties? > 2. Short of a code scan for references to Jenkins#proxy, do we know > which plugins support a proxy server through this mechanism? > Alternatively, *if you've tested your plugin behind a proxy, please > reply with a row to add to the table.* > 3. Anything else we should add? For example, would this page be a > good place for information on adding/testing proxy support to a plugin or > should we put that in the plugins developer guide? > > Thanks! > - Oli > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/5f49a5a1-af60-47f3-a922-3356419b451e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/5f49a5a1-af60-47f3-a922-3356419b451e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CABffhO63QfD8zcmqOj7fg23a1t%2BrCt9FeAguOt8ytrNPDYcRRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
