-
Notifications
You must be signed in to change notification settings - Fork 196
Open
Open
Copy link
Labels
API interactionsClarification neededAdditional clarification neededAdditional clarification neededlock queue priority and visibility
Milestone
Description
What feature do you want to see added?
Afaict the current usages of lock is to prevent subsequent runs from entering the current code section. However, I am trying to find a way to do the opposite, namely cancel any current jobs that have the given lock. I couldn't find a way do that even when considering skipIfLocked.
The workflow to support would be something like this:
JobAcalculates the label for the lockJobAcreates the lock and starts doing a long jobJobBis triggered and it calculates the same label for the lockJobBruns a snippet and cancelsJobA, triggering a cleanup job for its current long jobJobBprocedes to create the lock and stats doing its long job
What I am trying to support here that disableConcurrentBuilds(abortPrevious: true) is to cancel the current running jobs that have a specific set of parameters, while the option disableConcurrentBuilds seems like it would cancel any job in the current piepline.
Upstream changes
No response
Are you interested in contributing this feature?
No response
Metadata
Metadata
Assignees
Labels
API interactionsClarification neededAdditional clarification neededAdditional clarification neededlock queue priority and visibility