I have a question about stages.
In https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#stages
it is stated that:
Newer builds are always given priority when entering such a throttled
> stage; older builds will simply exit early if they are preëmpted.
>
I have two throttled stages like this:
stage name: 'publish', concurrency: 1
flow.publish()
stage name: 'qadeploy', concurrency: 1
input message: "Tag and deploy QA env?"
flow.qadeploy()
Where flow is an object loaded from flow.groovy, and the qadeploy() method
is handling 'node{ ... }' allocation etc.
What I see is that the newest build is waiting for at the throttled stage
which is waiting for a human to answer the question.
As a programmer I understand why this is happening, but I don't understand
how to structure the flow to be able to answer yes/no to only the newest
build and make an older build 'exit early'. If I move the input message
before the stage start the newest build just waits to enter 'publish'
instead of 'qadeploy'.
I really like the concepts and principles behind the workflow-plugin(s) but
I am struggling to like the implementation and usability of the suite...
--
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/e81eae49-24f5-4009-ab1e-957f6869cf96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
