[JIRA] (JENKINS-37895) Option to "skip" a locked section if a newer build already completed it

1 view
Skip to first unread message

r.baeriswyl@gmail.com (JIRA)

unread,
Sep 1, 2016, 10:30:01 AM9/1/16
to jenkinsc...@googlegroups.com
Roman Baeriswyl created an issue
 
Jenkins / Improvement JENKINS-37895
Option to "skip" a locked section if a newer build already completed it
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: lockable-resources-plugin
Created: 2016/Sep/01 2:29 PM
Priority: Minor Minor
Reporter: Roman Baeriswyl

It would be great to have an option that when an older build finally gets a lock it can skip it because a newer build already completed it.
Example:
Start build 1
Start build 2
build 2 reaches locked block
build 1 reaches locked block
build 2 executes locked block (eg sonarqube scanner or deployment)
build 2 frees the lock
build 1 gets the lock
build 1 skips block in the lock because a newer build already completed it

As far as I understand this cannot be done right now. Would be really handy to have this.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

r.baeriswyl@gmail.com (JIRA)

unread,
Sep 2, 2016, 4:52:02 AM9/2/16
to jenkinsc...@googlegroups.com
Roman Baeriswyl commented on Improvement JENKINS-37895
 
Re: Option to "skip" a locked section if a newer build already completed it

Regarding the documentation, the concurrency property of a Stage (which is now deprecated) could exactly do this:

The stage command lets you mark certain sections of a build as being constrained by limited concurrency (or, later, unconstrained). Newer builds are always given priority when entering such a throttled stage; older builds will simply exit early if they are preëmpted.

This really is now a missing feature for me.

r.baeriswyl@gmail.com (JIRA)

unread,
Sep 2, 2016, 5:07:01 AM9/2/16
to jenkinsc...@googlegroups.com

Just found out that this should be possible to achieve with the milestone step. Hopefully that will get released soon.

r.baeriswyl@gmail.com (JIRA)

unread,
Sep 7, 2016, 2:38:01 AM9/7/16
to jenkinsc...@googlegroups.com

tobias-jenkins@23.gs (JIRA)

unread,
Oct 12, 2019, 6:03:01 PM10/12/19
to jenkinsc...@googlegroups.com
Tobias Gruetzmacher resolved as Won't Do
 

This seems to need quite a lot of tracking and I currently consider this out of scope for the lockable-resources plugin. Feel free to reopen if you think otherwise.

Change By: Tobias Gruetzmacher
Status: Open Resolved
Resolution: Won't Do
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages