Better use the throttle concurrent build plugin IMO. Works fine for us:
Define a central token. Then configure both job to "acquire" it when starting. Done. Both jobs won't run at the same time.
Cheers
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/36f5d31e-2800-42f7-ae71-97ccd274331d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Better use the throttle concurrent build plugin IMO. Works fine for us:
Define a central token. Then configure both job to "acquire" it when starting. Done. Both jobs won't run at the same time.
Le 21 mai 2015 8:59 AM, "tps800" <t...@vr-web.de> a écrit :
>
> On Tuesday, May 19, 2015 at 5:58:12 PM UTC+2, Baptiste Mathus wrote:
>>
>> Better use the throttle concurrent build plugin IMO. Works fine for us:
>>
>> Define a central token. Then configure both job to "acquire" it when starting. Done. Both jobs won't run at the same time.
>
> This plugin isn't as easy to handle (you've to create a central token)
Yes that's indeed the only impediment we have identified with this plugin: requiring to be admin to create a token is overkill.
We (software factory admins) would like to propose an improvement PR about this, but not top priority at the moment...
Cheers
-- Baptiste
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5hiPi19bz-Dcj53uoSMT%3DQe8nUSEaQ5bwBeQLkTY782w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADROnO9k9gHky2TxcJR%2BxbcRRZCjNetahxdfDWtjJa7rqg6DDQ%40mail.gmail.com.