In your pipeline, the *node* parameter can take an argument of which node to run on.
See this example: https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test.groovy#L100 In my job, I defined BUILD_NODE with the NodeLabel Parameter Plugin ( https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin ). -- Craig On Mon, Jun 13, 2016 at 2:03 PM, Eli White <[email protected]> wrote: > We follow the Jenkins configuration best practices and have no executors > on our master node and force everything to run on our agents. > > We are starting to work with pipeline jobs and are worried that bad > Jenkinsfiles could cause problems on our master. > How can we force the flyweight jobs to run on a designated machine *other* > than master? > > How do other people handle this? > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/d4ee67f4-ab75-4a1e-9883-69453bdd656b%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/d4ee67f4-ab75-4a1e-9883-69453bdd656b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVdn8jc2EUH77KYYxw0ghcsgo_eCt8rycn20oP5xuqEeAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
