jenkinsci / jenkinsci/lockable-resources-plugin

Pipeline stage not shown in queue while waiting for resource

Open
#102 2 comments 0 reactions 0 assignees View on GitHub
resource conflicts or cleanup handled poorly Triage ui
Dominant language
Java
Stars
99
Forks
205
Avg merge
2d 13h
Merged PRs (30d)
8

Description

I recently switched from

```
lock('LOCK') {
stage('Integration test') {
# Doing stuff
}
}
```

to

```
stage('Integration test') {
options {
lock('LOCK')
}
# Doing stuff
}
```

The reason was to avoid having an executor slot occupied while waiting for the resource.
I expected the build to instead be shown in the build queue as non Pipeline builds are while waiting for a resource. But this is not the case, instead the build is invisible until the resource is acquired.

Contributor guide

Open the contributing guide

Research direction

Compare the two Declarative Pipeline examples in the issue and investigate how the pipeline stage behaves while its lockable resource is unavailable. The work is done when the waiting build is visible in the Jenkins build queue, as expected for non-Pipeline builds, without occupying an executor.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.