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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/098bab82-0336-468f-8aa5-415b6e457a57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to