-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.7
Promoted Builds plugin ver 2.2.7
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like $PROMOTED_USER_NAME and $PROMOTED_SVN_REVISION) still work just fine. And promotion parameters work fine, too.
But parameters of the build being promoted are no longer replaced – the parameter text remains unchanged in the tasks executed during the promotion. The build parameters are still available during the initial build, but don't seem to be available during the promotion run.
In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion.
- depends on
-
-
- Resolved
-
[JENKINS-36120] Parameterized build parameters no longer available during promotion
Patrick Conant
created issue -
Patrick Conant
made changes -
| Description |
Original:
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like ${PROMOTED_USER_NAME} and ${PROMOTED_SVN_REVISION}) still work just fine. And promotion parameters work fine, too. But parameters of the build being promoted are no longer replaced -- the parameter text ("${SERVICE_NAME}") remains unchanged in the tasks executed during the promotion. The build parameters _are_ still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion. |
New:
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like {{${PROMOTED_USER_NAME}}} and {{${PROMOTED_SVN_REVISION}}}) still work just fine. And promotion parameters work fine, too. But parameters of the build being promoted are no longer replaced -- the parameter text ("${SERVICE_NAME}") remains unchanged in the tasks executed during the promotion. The build parameters _are_ still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion. |
Patrick Conant
made changes -
| Description |
Original:
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like {{${PROMOTED_USER_NAME}}} and {{${PROMOTED_SVN_REVISION}}}) still work just fine. And promotion parameters work fine, too. But parameters of the build being promoted are no longer replaced -- the parameter text ("${SERVICE_NAME}") remains unchanged in the tasks executed during the promotion. The build parameters _are_ still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion. |
New:
Following a migration from Jenkins 1.x to 2.2.7, the 'promoted build' plugin stopped replacing most of the variables that we rely on. The PROMOTED_* built-in variables (like $PROMOTED_USER_NAME and $PROMOTED_SVN_REVISION) still work just fine. And promotion parameters work fine, too. But parameters of the build being promoted are no longer replaced -- the parameter text remains unchanged in the tasks executed during the promotion. The build parameters _are_ still available during the initial build, but don't seem to be available during the promotion run. In our particular case, we're using the variables in the extended e-mail publisher during promotion, but I've also verified the same problem when using a simple shell script in the promotion. |
| Workflow | Original: JNJira [ 172773 ] | New: JNJira + In-Review [ 184769 ] |
We are experiencing this (or something very similar).
We have a job that runs, compiles and tests. Prior to upgrade the injected paramaters to that 'build' job (from gradle.properties, like "version=<version>") were available to the downstream job in the promotion when we enabled "current build parameters" in the promotion configuration. They are no longer available in 2.24. This is more then an annoyance ... it's a workflow issue. I'd rather have the default security policy deal with the security setting as an "opt-in" for those servers running outside of a firewall (which seems pretty low volume).
Michael Fowler
made changes -
| Link |
New:
This issue depends on |
FWIW, adding the hudson.model.ParametersAction.keepUndefinedParameters parameter (as documented in the Jenkins Security Advisory 2016-05-11) proved to be a suitable workaround for our scenarios.