I think you would need the NodeLabel Parameter Plugin. And as Craig
Rodrigues recently posted, that plugin is not yet compatible with
Workflow, although he has proposed a fix:
==========
*Re: [workflow-plugin] Example using NodeLabel Parameter plugin?*
It turns out that the NodeLabel Parameter plugin doesn't work with the
workflow plugin:
https://issues.jenkins-ci.org/browse/JENKINS-32209
I submitted this fix:
https://github.com/jenkinsci/nodelabelparameter-plugin/pull/10
--
Craig
===========
On 1/21/2016 11:53 AM, Patrick Bruneton wrote:
No because I would have to restrict the jobs on a particular slaves.
I have many windows slaves.
If job 'build' gets executed on windows-slave-1 I want the 'test' to
be executed on the same slave (and be executed immediately)
Le jeudi 21 janvier 2016 17:21:33 UTC+1, Brian Ray a écrit :
Can you just set the *Restrict where this project can be run*
checkbox in conjunction with the *Label Expression* param on the
two subjobs?
On Thursday, January 21, 2016 at 2:16:39 AM UTC-8, Patrick
Bruneton wrote:
Hi all,
I am trying to implement a use case with the workflow plugin.
I have two jobs, say build & test, that I want to run inside a
pipeline. Sounds easy.
But I have a constraint:I want the two jobs to executed on the
same slave.
So I tried something like this:
|
node('windows'){
stage name:'Build',concurrency:1
build 'build'
stage name:'Test',concurrency:1
build 'test'
}
|
But 'build' and 'test' are executed in their own slave, which
is not the one allocated by 'node'. That seems logical.
Is there a way to force the builds to run a node?
I understand I could(/should) write the job logic directly in
the pipeline, e.g.
|
node('windows'){
stage name:'Build',concurrency:1
// build stage details
stage name: 'Test', concurrency: 1
// test stage details
}
|
However, I am not sure I can do this, because my jobs exist
already, and use plugins that do not seem to be supported by
workflow (e.g. xUnit, Extended Email)
Any thought?
Thanks,
Patrick
--
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
<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/413e8e29-f03c-406d-b1d1-7a8cc7964ee7%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/413e8e29-f03c-406d-b1d1-7a8cc7964ee7%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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/56A1310F.8010609%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.
