jenkinsci / jenkinsci/matrix-project-plugin
[JENKINS-21179] Touchstone: execute further configurations independent from the result
- Dominant language
- Java
- Stars
- 17
- Forks
- 85
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 5
Description
I have a matrix project configured like this:
Server A
Server B
Config 1
Config 2
Both servers are independent from each other and can be used at the same time. But because of shared resources "Config 1" and "Config 2" must not be executed at the same time on the same server.
Via a touchstone setting for "Config 1" we can achive this but "Config 2" will only be executed if the result of "Config 1" is at least "unstable".
In my case the result of "Config 1" is not important for the execution of "Config 2" -> I would like to have a "Execute always" setting for the touchstone result.
---
Originally reported by blorenz, imported from: Touchstone: execute further configurations independent from the result
Raw content of original issue
I have a matrix project configured like this:
Server A
Server BConfig 1
Config 2
Both servers are independent from each other and can be used at the same time. But because of shared resources "Config 1" and "Config 2" must not be executed at the same time on the same server.
Via a touchstone setting for "Config 1" we can achive this but "Config 2" will only be executed if the result of "Config 1" is at least "unstable".
In my case the result of "Config 1" is not important for the execution of "Config 2" -> I would like to have a "Execute always" setting for the touchstone result.
Contributor guide
Research direction
Start by locating the matrix-project-plugin code that evaluates Touchstone results and schedules configurations; the payload names no specific files, tests, or entry points. Trace how Config 1's result gates Config 2, then verify an “Execute always” option preserves same-server serialization while allowing independent servers to run concurrently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100