jenkinsci / jenkinsci/release-plugin
[JENKINS-10551] Check the parameter from upstream job to trigger a release build
- Dominant language
- Java
- Stars
- 24
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
The Release plugin allows to manually trigger a build with specific settings.
However there is no way to trigger the same by passing the parameters from upstream build.
We can pass the paramters using the "Parameterized Trigger Plugin" but the build won't be marked as a "Release" (with the nice action icon and description) and kept forever.
Ideally I would like to have a way to "upgrade" from normal build to release build when a parameter is present.
---
Originally reported by fct, imported from: Check the parameter from upstream job to trigger a release build
petehayes
Raw content of original issue
The Release plugin allows to manually trigger a build with specific settings.
However there is no way to trigger the same by passing the parameters from upstream build.
We can pass the paramters using the "Parameterized Trigger Plugin" but the build won't be marked as a "Release" (with the nice action icon and description) and kept forever.Ideally I would like to have a way to "upgrade" from normal build to release build when a parameter is present.
Contributor guide
Research direction
Start by reading the release-plugin handling for manually triggered release builds and how parameters arrive from the Parameterized Trigger Plugin. Confirm how a parameter could mark an upstream-triggered build as a release, including its action icon, description, and retention behavior; done means the requested upgrade path is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100