On 2021-01-04T22:33:55 +0100
ST <st.mailingli...@gmail.com> wrote:
> As mentioned by Mark, nodesByLabel will give you control over what agents
> are currently available. But you will need a script {} section in an
> initialization stage and probably set an env variable that you then check
> in the when {} section of the windows stages. So not purely declarative
> anymore.
>
> Another idea (in case you are not aware of this yet) would be to set a very
> short *stage-specific timeout* for the windows stages only. The windows
> stages will then show as ABORTED, but since the Linux stages are run in
> parallel they should still go ahead and run.
> Stage timeout documentation:
> https://www.jenkins.io/doc/book/pipeline/syntax/#stage-optionsThanks, both of you! I think I might go another way: Throw hardware at the problem and arrange to have a Windows node that's actually on 24/7. -- Mark Raynsford | https://www.io7m.com -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20210105213434.6ea0e6fa%40sunflower.int.arc7.info.
pgpu2L2idLm_Q.pgp
Description: OpenPGP digital signature
