Again answering to self:
If i modify my script to be like the below, i can still confine my files to
a workspace and use the checkpoint
stage name 'one', concurrency: 1
node(XXX) {
ws("C:\\abc\\workspace\\${env.BUILD_NUMBER}") {
// codes //
}
}
checkpoint 'post1'
stage name 'two', concurrency: 2
node(XXX) {
ws("C:\\abc\\workspace\\${env.BUILD_NUMBER}") {
// codes //
}
}
On Tuesday, February 2, 2016 at 10:35:09 AM UTC-6, niristotle okram wrote:
>
> Due to some requirements of confining the files in the workspace on an
> instance of a job, i am restricting instances of job to a particular node &
> specific workspace. The reason for clamping down the node is to avoid
> overwriting when the concurrent builds are executed. The workflow script
> looks like below:
>
> node(XXX) {
> ws("C:\\abc\\workspace\\${env.BUILD_NUMBER}") {
>
> // codes of all the stages //
>
> }
>
> }
>
> I get the warnings: Using checkpoint inside of node {} is unsupported and
> unreliable
>
> Do i stop using the checkpoint with my current workflow script design?
>
>
--
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/ad50c48f-ab6d-4620-a828-da37cc16707d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
