jenkinsci / jenkinsci/lockable-resources-plugin

[JENKINS-69612] Ability to add resource specific configuration parameters to lockable resource

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

Description

Currently lockable resource purpose is to detect overlap of resource using. It's a wonderful feature and is intuitively CI pipeline tool responsilble and removes need for external reservation dependecies.

Another external dependency is (probably) needed for telling what configuration paramaters resource have which impact build or test automation execution. That would be included to lockable resource. I suggest to give environment variables to build use from locablre resource.

Eg. configure lockable resource to have value

CONNECTED_MOBILE_PHONE=5

And using Jenkins build has e.g. environment variable

RESOURCE_CONNECTED_MOBILE_PHONE

---
Originally reported by juhoarvid, imported from: Ability to add resource specific configuration parameters to lockable resource


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

Raw content of original issue

Currently lockable resource purpose is to detect overlap of resource using. It's a wonderful feature and is intuitively CI pipeline tool responsilble and removes need for external reservation dependecies.
Another external dependency is (probably) needed for telling what configuration paramaters resource have which impact build or test automation execution. That would be included to lockable resource. I suggest to give environment variables to build use from locablre resource.

Eg. configure lockable resource to have value
CONNECTED_MOBILE_PHONE=5
And using Jenkins build has e.g. environment variable
RESOURCE_CONNECTED_MOBILE_PHONE

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reviewing how the lockable-resources-plugin represents resource configuration and exposes values to builds, then clarify the expected parameter naming and scoping; done means resource-specific configuration is available to the build as documented environment variables.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.