• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: git-plugin
• Labels:

  None
• Environment:

  git-plugin 2.4.1
  Jenkins 1.643

[JENKINS-32218] buildsByBranchName is not set anymore

Alex Nederlof created issue - 2015-12-29 15:03

Mark Waite made changes - 2015-12-30 01:08

Description

Original: I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one. This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible.

New: _emphasized text_I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one. This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible.

Mark Waite made changes - 2015-12-30 01:25

Description

Original: _emphasized text_I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one. This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible.

New: I noticed that GIT_PREVIOUS_SUCCESSFUL_COMMIT was not set anymore on the Job that only builds our master branch. After some digging I found out that since the upgrade from the previous version (I can't find which version that was, is that stored somewhere?) the buildsByBranchName variable in any `build.xml` is not set anymore (it's empty). It is set in other jobs we have, just not this one. This env is critical for us, so I'm going to try to rollback. I'm glad to help track down this problem if possible.

Mark Waite made changes - 2016-02-01 05:20

Link

New: This issue is related to JENKINS-29482 [ JENKINS-29482 ]

Mark Waite made changes - 2016-02-02 13:04

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

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

Workflow

Original: JNJira [ 167799 ]

New: JNJira + In-Review [ 198278 ]

Jesse Glick made changes - 2016-10-20 19:23

Link

New: This issue is related to JENKINS-19022 [ JENKINS-19022 ]

Mark Waite made changes - 2019-10-23 01:28

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]