Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56091

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

XMLWordPrintable

      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

          Marcus Schulmann added a comment -

          This seems to be the same as https://issues.jenkins-ci.org/browse/JENKINS-35905

          Marcus Schulmann added a comment - This seems to be the same as  https://issues.jenkins-ci.org/browse/JENKINS-35905

            surenpi Rick
            rthurner rupert je thurner
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: