[JIRA] (JENKINS-56091) no agent with label available clogs pipeline, should fail automatically instead of waiting

rupert je thurner updated an issue

Jenkins / JENKINS-56091

no agent with label available clogs pipeline, should fail automatically instead of waiting

Change By:	rupert je thurner

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}
 

 

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.