[JIRA] (JENKINS-44411) Support throttling of blocks without node() in the throttle() step

[cyberjoac@gmail.com (JIRA)]

Joachim Hagege commented on JENKINS-44411

Re: Support throttling of blocks without node() in the throttle() step Hi, any update on support of declarative pipeline flows ?  Thanks Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[simon.kaufmann@adesso.ch (JIRA)]

Simon K commented on JENKINS-44411

Re: Support throttling of blocks without node() in the throttle() step

Hi, we switched to the lock-Plugin for this use case: https://wiki.jenkins.io/display/JENKINS/Lockable+Resources+Plugin Worked as aspected

Add Comment

[marcus.a.philip@gmail.com (JIRA)]

Marcus Philip commented on JENKINS-44411

Re: Support throttling of blocks without node() in the throttle() step

Lockable resources solves some use cases in declarative pipelines, but not all. I want to limit builds of a declarative pipeline project to one build per node. I can't achieve this.

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[marcus.a.philip@gmail.com (JIRA)]

Marcus Philip edited a comment on JENKINS-44411

Re: Support throttling of blocks without node() in the throttle() step

Lockable resources solves some use cases in declarative pipelines, but not all. I want to limit builds of a declarative pipeline project to one build per node. I can't achieve this.

The documentation in "Example 3: Throttling of declarative pipelines" is lacking/misguiding. I've tested, and it has no throttling effect on a single declarative Pipeline job. Does it only throttle between jobs using same category? (And in that case, are different branches in a multi-branch pipeline considered different jobs?) IMHO, that feature is not as useful as being able to throttle on the same job.

Add Comment