jenkinsci / jenkinsci/lockable-resources-plugin

[JENKINS-38852] Allow exclusive vs. shared locks on resources

Open
#858 0 comments 0 reactions 0 assignees View on GitHub
approved component:lockable-resources-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
99
Forks
205
Avg merge
2d 13h
Merged PRs (30d)
8

Description

I'd like to distinguish between shared and exclusive resources.

Example:



  • exclusive lock: while a database is being rebuilt, all other jobs need to wait

  • shared lock: after the database has been rebuilt, multiple can use it (i.e. to read data)

The current workaround is to use "flock" Linux shell command to achieve this, but this only works when everything runs on one node.

This has been suggested here JENKINS-1990">JENKINS-1990 - but the locks-and-latches plugin seems to be dead. I also want this as part of the lockable-resource-plugin, as this supports the new pipeline syntax.

---
Originally reported by ahus1, imported from: Allow exclusive vs. shared locks on resources


  • status: Open
  • priority: Minor
  • component(s): lockable-resources-plugin
  • resolution: Unresolved
  • votes: 5
  • watchers: 5
  • imported: 20251217-081411

Raw content of original issue

I'd like to distinguish between shared and exclusive resources.

Example:



  • exclusive lock: while a database is being rebuilt, all other jobs need to wait

  • shared lock: after the database has been rebuilt, multiple can use it (i.e. to read data)

The current workaround is to use "flock" Linux shell command to achieve this, but this only works when everything runs on one node.

This has been suggested here JENKINS-1990 - but the locks-and-latches plugin seems to be dead. I also want this as part of the lockable-resource-plugin, as this supports the new pipeline syntax.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.