Jenkins and Windows

[Ian Young]

> On 12 Jan 2016, at 18:07, Tom Zeller <tzeller at dragonacea.biz> wrote:
> 
> “Add a node/slave axis” : We could add a node/slave axis much like our JDK axis.

I'd say this sounds like the best option, and having these various platform axes all integrated into one job per project is much more scalable than the alternatives.

> One downside I see is losing the automatic configuration of triggering downstream projects. Not a big deal, we can manually configure our project/job hierarchy as we have done elsewhere (e.g. trigger-nightly-v3), which actually might be considered a positive.

Agreed. The SCM-triggered and overnight jobs (e.g., *-multi) are quite different, and only the former really needs the automatic triggering.

> “Add parameterization to existing jobs” : We could add and configure plugins to Jenkins, like the Node/Label Parameter Plugin, to re-configure our existing jobs to run on Windows as well as Linux. I tried this option first, but had trouble with recursion. As with any plugin, there is a bit of conflict with built-in Jenkins functionality (“require label when building”).

I find Jenkins plugins about as inscrutable as Maven ones and I'm not surprised you ran into problems. Any solution that doesn't involve more Jenkins plugins has a substantial advantage in my mind.

> The follow-up is whether we want certain/all jobs to pass on Windows before deploying snapshots. We could start building and deploying snapshots of the Windows installer via Jenkins on the Windows slave, much like the V3-nightly jobs do now.

I don't think that's necessary, particularly if we have any questions about whether the Windows slave will be 100% available.

> If we go with “add a platform axis”, we might want to rename *-multi-jdk to something else, maybe just *-multi, but that’s not a big deal either.

Agreed.

    -- Ian




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3563 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/dev/attachments/20160114/daf3c32b/attachment.p7s>