• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: promoted-builds-plugin
• Labels:

  None
• Environment:

  Jenkins ver. 2.7
  Promoted Builds plugin ver 2.2.7
  

[JENKINS-36120] Parameterized build parameters no longer available during promotion

Patrick Conant created issue - 2016-06-21 20:29

Patrick Conant made changes - 2016-06-21 20:31

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 - 2016-06-21 20:33

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.

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

Original: JNJira [ 172773 ]

New: JNJira + In-Review [ 184769 ]

Michael Fowler made changes - 2016-12-21 18:58

Link

New: This issue depends on JENKINS-14169 [ JENKINS-14169 ]