Jenkins que and node labels
5 views
Skip to first unread message
Andrej Gukov
Jan 12, 2015, 4:37:06 AM1/12/15
to jenkins...@googlegroups.com
Hello,
We have a tricky structure of parallel flows inside flows and we need to lock some of the flows after they finish.
The solution currently is to change node label of the flow to non existent one via API, and change it back when all the flows finish. Somehow while builds are in que they can still get the changes in "Restrict where this project can be run" field
The question is: Is anyone familiar with this feature (qued jobs updating parameter of node label) and if anyone knows is it a bug or a feature, is it safe to base our logic on this feature and not fear that it will be "fixed" somewhere down the line
We have a tricky structure of parallel flows inside flows and we need to lock some of the flows after they finish.
The solution currently is to change node label of the flow to non existent one via API, and change it back when all the flows finish. Somehow while builds are in que they can still get the changes in "Restrict where this project can be run" field
The question is: Is anyone familiar with this feature (qued jobs updating parameter of node label) and if anyone knows is it a bug or a feature, is it safe to base our logic on this feature and not fear that it will be "fixed" somewhere down the line
Reply all
Reply to author
Forward
0 new messages