Details
-
Type:
New Feature
-
Status: Reopened (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: plugin-proposals
-
Labels:None
-
Environment:Jenkins 1.642
github-branch-source-plugin:1.7
github-organization-folder-plugin:1.3
-
Similar Issues:
Description
Issue
When a node label does not exists, the build hangs in the queue until a node is assigned to that label. In that case I would like my build to fail. It would be great to have such option and also the possibility to apply it with GitHub Organization.
How to Reproduce
node ('thislabeldoesnotexists') { echo "This could be improved" }
This label does not exists in my Instance, the build hang in the queue and the console logs show:
> There are no nodes with the label ‘thislabeldoesnotexists’
Attachments
Issue Links
- is related to
-
JENKINS-41569 Pipeline hangs waiting for resume on an agent which never was
-
- Closed
-
-
JENKINS-40466 Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node
-
- Resolved
-
- links to
Activity
I totally agree with Marcus Schulmann, sometimes there is a uniqe agent (with specific hardware, for instance) used for tests. I wonder what can we do in order to bump this issue's importance and handling?
Amit Dar
added a comment - I totally agree with Marcus Schulmann , sometimes there is a uniqe agent (with specific hardware, for instance) used for tests. I wonder what can we do in order to bump this issue's importance and handling? Timeout would be very useful.
ipleten
added a comment - Timeout would be very useful. This is causing us serious problems as well. I thought the labels would be looked at as tags. If there is no match, no big deal, simply skip it. I mean, think about it. I can have a label defined like "prod || test || development" and if I have so much as one node matching any of those labels I'm fine. If all I had was a node with a label of prod, and no test or development nodes, no problem. But all of a sudden if I don't match on prod, it hangs in the queue? No, just skip it, like you would skip any node that doesn't match the label. This is messing up our whole paradigm because we have one set of jobs that are source controlled so that we don't have all these variants all over the place. But because of this, it doesn't work.
Jason Perrone
added a comment - This is causing us serious problems as well. I thought the labels would be looked at as tags. If there is no match, no big deal, simply skip it. I mean, think about it. I can have a label defined like "prod || test || development" and if I have so much as one node matching any of those labels I'm fine. If all I had was a node with a label of prod, and no test or development nodes, no problem. But all of a sudden if I don't match on prod, it hangs in the queue? No, just skip it, like you would skip any node that doesn't match the label. This is messing up our whole paradigm because we have one set of jobs that are source controlled so that we don't have all these variants all over the place. But because of this, it doesn't work. Totally agree that this is needed! We have the same situation as Dar mentioned. Sometimes ja job get stuck and then the queue gets full, eventually we end up with a mess. Now the recovery requires manual intervention purging the queue etc...
I wonder why this is still not yet implemented. This clogged our whole build-pipeline over the weekend because one agent was down, which was needed for specific tests.