Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32218

buildsByBranchName is not set anymore

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • git-plugin
    • None
    • git-plugin 2.4.1
      Jenkins 1.643

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-19022 GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29482 Prune stale branches prevents git plugin change history display

          • Major - Major loss of function.
          • Closed

          Activity

            People

              markewaite Mark Waite
              alexnederlof Alex Nederlof
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: