• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • Windows 7 64Bit, jenkins 1.600

      Since the update to jenkins 1.600 every project has the BUILDID and BUILD_TAG from previous project:

      BUILD_DISPLAY_NAME=#1964
      BUILD_ID=442
      BUILD_NUMBER=442
      BUILD_TAG=jenkins-ImageVision_1-442
      BUILD_URL=http://heilbutt:8080/job/DiaShow_Easy/1964/

      While I'm not happy that for some time now the BUILD_ID has been the same number as the BUILD_DISPLAY_NAME instead of a timestamp, this new discrepancy needs to be fixed quickly.

          [JENKINS-27188] BUILDID and BUILD_TAG from previous project

          Kerstin Thaler created issue -

          Daniel Beck added a comment -

          Are you using env-inject? If so, this may be related to JENKINS-27178.

          Daniel Beck added a comment - Are you using env-inject? If so, this may be related to JENKINS-27178 .

          No, I don't use env-inject, and luckily so far I didn't run into any other errors.
          But I will switch back to 1.599 as well.

          Kerstin Thaler added a comment - No, I don't use env-inject, and luckily so far I didn't run into any other errors. But I will switch back to 1.599 as well.
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-27178 [ JENKINS-27178 ]

          Daniel Beck added a comment -

          FWIW my branch of 1.600 with the fix for JENKINS-27178 (see comments there) prevents this issue from occurring on my test instance as well.

          Daniel Beck added a comment - FWIW my branch of 1.600 with the fix for JENKINS-27178 (see comments there) prevents this issue from occurring on my test instance as well.

          Daniel Beck added a comment - - edited

          I can only reproduce this problem on 1.600 with env-inject installed and enabled. Without it, this issue doesn't occur. Could you double-check whether the plugin is installed and enabled? It doesn't have to be used in any jobs or nodes.

          Daniel Beck added a comment - - edited I can only reproduce this problem on 1.600 with env-inject installed and enabled. Without it, this issue doesn't occur. Could you double-check whether the plugin is installed and enabled? It doesn't have to be used in any jobs or nodes.

          Daniel Beck added a comment -

          Someone mentioned on #jenkins that they experience the wrong WORKSPACE being set for their jobs.

          [2015-03-02 10:31:40] <Johnou_> has anyone else experienced WORKSPACE job variable pointing to the incorrect job dir?

          That may be this issue as well.

          Daniel Beck added a comment - Someone mentioned on #jenkins that they experience the wrong WORKSPACE being set for their jobs. [2015-03-02 10:31:40] <Johnou_> has anyone else experienced WORKSPACE job variable pointing to the incorrect job dir? That may be this issue as well.

          Yes, I do have env-inject installed and enabled.

          Kerstin Thaler added a comment - Yes, I do have env-inject installed and enabled.
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-26755 [ JENKINS-26755 ]

          Daniel Beck added a comment -

          Alright, we see the same issue then.

          Also,

          [2015-03-02 11:14:58] <Johnou_> BUILD_TAG is incorrect as well
          [2015-03-02 11:15:13] <Johnou_> i did trawl through jira but I was looking for WORKSPACE
          [2015-03-02 11:15:32] <Johnou_> yes we use the envinject plugin

          Daniel Beck added a comment - Alright, we see the same issue then. Also, [2015-03-02 11:14:58] <Johnou_> BUILD_TAG is incorrect as well [2015-03-02 11:15:13] <Johnou_> i did trawl through jira but I was looking for WORKSPACE [2015-03-02 11:15:32] <Johnou_> yes we use the envinject plugin

            ndeloof Nicolas De Loof
            pfennig59 Kerstin Thaler
            Votes:
            4 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: