On Fri, Jan 9, 2015 at 11:15 AM, Bowen Cheng <[email protected]> wrote: > how to let ATH spawn two accessible Jenkins instances
CloudBees does this for Jenkins Operations Center acceptance tests, which must start up both JOC (essentially a very customized Jenkins distribution) and a regular Jenkins master, connect them, and then perform some operations spanning the two servers. I did not write it, but it seems like it adds another JenkinsControllerFactory with a distinct ID, and adds a AbstractModule implements ExtensionModule. It also lets you use JUT to speed up tests (one server for JOC, one server for the attached Jenkins). Currently it does not make any special use of Docker; both servers are just started as local processes by default (on different ports of course, with different $JENKINS_HOME directories). It does not look like this (non-OSS) code is directly reusable in another context, but perhaps the basic idea could be duplicated in either ATH itself or a separate extension to ATH that runs tests for one of the handful of OSS plugins that deal with multiple masters: job-import-plugin, build-publisher, etc. The additional test coverage from such an effort would not be very important, but it would serve as a working model of how to do this. @Kohsuke WDYT? -- 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/CANfRfr33%2B4AXLGm-33Mja9LGXGdvKi1GPCK8mrNAoFQp7-9ATg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
