-
Bug
-
Resolution: Unresolved
-
Critical
in a larger jenkins installation projects can bring down jenkins by using a non-existing agent jenkins does keep the jobs despite. it would be great if jenkins could be configured to cancel such jobs with an error.
pipeline { // agent none to allow different agents for various steps agent none stages { stage('Build') { agent { label 'nonexisting' } steps {
[JENKINS-56091] no agent with label available clogs pipeline, should fail automatically instead of waiting
Description |
Original:
in a larger jenkins installation projects can bring down jenkins by using a non-existing agent jenkins does keep the jobs despite. {code:java} pipeline { // agent none to allow different agents for various steps agent none stages { stage('Build') { agent { label 'nonexisting' } steps { {code} |
New:
in a larger jenkins installation projects can bring down jenkins by using a non-existing agent jenkins does keep the jobs despite. it would be great if jenkins could be configured to cancel such jobs with an error. {code:java} pipeline { // agent none to allow different agents for various steps agent none stages { stage('Build') { agent { label 'nonexisting' } steps { {code} |
Description |
Original:
in a larger jenkins installation projects can bring down jenkins by using a non-existing agent jenkins does keep the jobs despite. it would be great if jenkins could be configured to cancel such jobs with an error. {code:java} pipeline { // agent none to allow different agents for various steps agent none stages { stage('Build') { agent { label 'nonexisting' } steps { {code} |
New:
in a larger jenkins installation projects can bring down jenkins by using a non-existing agent jenkins does keep the jobs despite. it would be great if jenkins could be configured to cancel such jobs with an error. {code:java} pipeline { // agent none to allow different agents for various steps agent none stages { stage('Build') { agent { label 'nonexisting' } steps { {code} |