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

rupert.thurner@credit-suisse.com (JIRA)

unread,

Feb 11, 2019, 2:02:04 PM2/11/19

to jenkinsc...@googlegroups.com

rupert je thurner created an issue

Jenkins /

JENKINS-56091

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

Issue Type:	Bug
Assignee:	Rick
Components:	agent-loadbalance-plugin
Created:	2019-02-11 19:01
Labels:	operation
Priority:	Critical
Reporter:	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.

 
                                                                pipeline {
    // agent none to allow different agents for various steps
    agent none
    stages {
        stage('Build') {
            agent {
                label 'nonexisting'
            }
            steps {
 
                                                            

Add Comment

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

rupert.thurner@credit-suisse.com (JIRA)

unread,

Feb 11, 2019, 2:05:01 PM2/11/19

to jenkinsc...@googlegroups.com

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}