Aleksandr Kazakov added a comment - 2017-12-14 18:17 For anyone who's struggling with this issue - we use a workaround. We use it for cloud providers but it can be adjusted and used for static slave nodes as well. We didn't use it in declarative pipeline, but I think this approach can be applied to it too.  We have a script in our shared library vars/node.groovy:   import org.jenkinsci.plugins.workflow.cps.DSL import hudson.model.Label import jenkins.model.Label import antlr.ANTLRException @NonCPS String checkLabel( String labelExpression) { String errorMessage = '' def clouds = Jenkins.instance.clouds if (clouds) { try { def label = Label.parseExpression(labelExpression) def labelMatchedCloud = clouds.find { it.canProvision(label) } if (!labelMatchedCloud) { errorMessage = "Cannot find a node with label ${labelExpression}" } } catch (ANTLRException e) { errorMessage = "Invalid node label expression:\n${e.message}" } } return errorMessage } def call(Closure body) { error """No label specified. Usage: node( '<<you_label_1>> && <<your_label_2>>' ) { ... }""" } def call( String label, Closure body) { def errorMessage = checkLabel(label) if (errorMessage) { error errorMessage } DSL steps = getBinding().getVariable( 'steps' ) as DSL steps.invokeMethod( 'node' , [label, body] as Object []) } Jenkinsfile   @Library( 'myFancyLibrary@version' ) node( 'label1 && label2' ) { // method from the lib is used ... }      

Adity Sreekumar added a comment - 2018-05-14 18:16 We are facing this issue currently on our builds as well on occasion as we migrate jobs from one jenkins server to another which is accompanied with associated node relabeling and addition of new nodes. What I thought made sense was if the timeout could be applied to the pipeline as a whole and not just a step.

Amit Dar added a comment - 2019-06-25 09:27 This option is a high valuable option for organizations using a main jenkins server handling jobs for various development and integration groups. this way, a job waiting for execution would be automatically removed from the build queue after a pre-defined time for machine provisioning and the built queue will stay "clean". a notification with the reason should also be viewable in the console output of the execution (though it was not executed at all...).

Marcus Schulmann added a comment - 2020-03-30 07:51 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.

Amit Dar added a comment - 2020-03-30 10:41 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?