Hi Domi, first a question about the suggested proxy library. I start the disucssion on 2 different threads to separate the topics. One issue we have is to get the right proxy settings on our master servers and the build nodes. We are running Jenkins in corporate environment with multiple data center locations, where each location has different proxy settings. The master (with its proxy configuration in the update manager) runs in data-center A and the build nodes in data-center B. There is currently no straight forward way to configure the proxy for each node separately We usually set the following properties for each build step/job:
* Java -> VM Parameters -Dhttp.proxyHost=http://...com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=... -Dhttps.proxyHost=http://...com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts=... * Bash -> Environment export http_proxy=http://...com:80 export https_proxy=http://...com:80 export no_proxy=... It would be interesting to have a proxy configuration per Jenkins node and a plugin that inserts the parameters into the environment or as VM parameters to the processes being launched: * JAVA_OPTS for some Java processes * ANT_OPTS for Ant Build Steps * MAVEN_OPTS for Maven Build Steps * GRADLE_OPTS for Gradle Builds Steps * ... How is the suggested library helping in this regard? The plugin wiki page says "... plugin also provides a utility class to help you get the proxyserver instance that is correct for the current jenkins instance.", but how is this achieved? Regards, Michael On Sun, May 13, 2012 at 9:40 AM, domi <[email protected]> wrote: > Michael, > I have granted you commit access to the plugins, but lets really talk about > merging the two plugins, I really think this would make sense and give a > great benefit for users. > e.g. global repositories are to be configured for both plugins otherwise. > regards Domi > > On 13.05.2012, at 09:22, domi wrote: > > > Hi Michael, > this is close to the functionality of this > plugin: https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin > I think we should check if it would make sense to merge the two… > About your proxy implementation, you should have a look at > this: https://wiki.jenkins-ci.org/display/JENKINS/Async+Http+Client+Plugin > what do you think? > regards Domi > > > On 12.05.2012, at 22:48, Michael Rumpf wrote: > > Hi, > > I have written a Maven Repository Client Plugin and put the source code on > github: > https://github.com/mrumpf/repoclient-plugin > > My github ID is "mrumpf". > > ### TODOs ### > * DONE Adapt pom.xml to Jenkins plugin structure > * Initial Wiki page created, but the plugin id is missing > https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repository+Client > * Add documentation > * Classification (Wiki Labels) > The plugin is behaving like a build wrapper, although it does not implement > the BuildWrapper API. > * CI Build > > Is there anything else left to do? > > Regards, > Michael > > >
