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

console display wrong build number when triggering a new build

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • None
    • Jenkins server on windows 7 64. Slaves on windows 7 32/64.

    Description

      I have a build which can trigger another build.
      In the console, I have at the end of the log:

      Triggering a new build of Build Hoops 3DX 5_x Windows Samples #1758
      Triggering a new build of Supervisor Test Windows Continuous #2831

      But I have not the same informations in Downstream build view.

      The good informations are in the Downstream build view.

      Attachments

        Issue Links

          Activity

            I have also seen this:
            Running Jenkins ver. 1.466.10.1 (Jenkins Enterprise by CloudBees 12.11)

            Two builds of different upstream jobs report triggering the same build # of a downstream job.

            tail of UPSTREAM1 build #48 console log:
            ...
            Sending email for trigger: Success
            Sending email to: ...
            Triggering a new build of DOWNSTREAM1 #157
            Triggering a new build of DOWNSTREAM2 #16298
            Finished: SUCCESS

            tail of UPSTREAM2 build #21 console log:
            ...
            Sending email to: aparn@amazon.com
            Triggering a new build of DOWNSTREAM1 #157
            Triggering a new build of DOWNSTREAM2 #16293
            Finished: SUCCESS

            head of DOWNSTREAM1 build #157 console log:
            Started by upstream project "UPSTREAM2" build number 21

            head of DOWNSTREAM1 build #160 console log:
            Started by upstream project "UPSTREAM2" build number 48

            geiger Richard Geiger added a comment - I have also seen this: Running Jenkins ver. 1.466.10.1 (Jenkins Enterprise by CloudBees 12.11) Two builds of different upstream jobs report triggering the same build # of a downstream job. tail of UPSTREAM1 build #48 console log: ... Sending email for trigger: Success Sending email to: ... Triggering a new build of DOWNSTREAM1 #157 Triggering a new build of DOWNSTREAM2 #16298 Finished: SUCCESS tail of UPSTREAM2 build #21 console log: ... Sending email to: aparn@amazon.com Triggering a new build of DOWNSTREAM1 #157 Triggering a new build of DOWNSTREAM2 #16293 Finished: SUCCESS head of DOWNSTREAM1 build #157 console log: Started by upstream project "UPSTREAM2" build number 21 head of DOWNSTREAM1 build #160 console log: Started by upstream project "UPSTREAM2" build number 48
            danielbeck Daniel Beck added a comment -

            There's no way to provide the information without waiting for the actually triggered build (see JENKINS-12827), so I decided to remove it to prevent further confusion:

            https://github.com/jenkinsci/jenkins/pull/1259

            danielbeck Daniel Beck added a comment - There's no way to provide the information without waiting for the actually triggered build (see JENKINS-12827 ), so I decided to remove it to prevent further confusion: https://github.com/jenkinsci/jenkins/pull/1259

            Code changed in jenkins
            User: Daniel Beck
            Path:
            core/src/main/java/hudson/tasks/BuildTrigger.java
            http://jenkins-ci.org/commit/jenkins/b401cf1fbafe50b67d1ed4aebef5bf2909e662e3
            Log:
            [FIX JENKINS-16827] Don't try to guess the build number

            The confusion resulting from a wrongly guessed build number isn't
            worth the minimal use this information provides.

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/b401cf1fbafe50b67d1ed4aebef5bf2909e662e3 Log: [FIX JENKINS-16827] Don't try to guess the build number The confusion resulting from a wrongly guessed build number isn't worth the minimal use this information provides.

            Code changed in jenkins
            User: Jesse Glick
            Path:
            core/src/main/java/hudson/tasks/BuildTrigger.java
            http://jenkins-ci.org/commit/jenkins/e6b063ddd43cd45dfab4ea9daa321f697985017a
            Log:
            Merge pull request #1259 from daniel-beck/JENKINS-16827

            [FIX JENKINS-16827] Don't try to guess the build number

            Compare: https://github.com/jenkinsci/jenkins/compare/a9c943798e5b...e6b063ddd43c

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/e6b063ddd43cd45dfab4ea9daa321f697985017a Log: Merge pull request #1259 from daniel-beck/ JENKINS-16827 [FIX JENKINS-16827] Don't try to guess the build number Compare: https://github.com/jenkinsci/jenkins/compare/a9c943798e5b...e6b063ddd43c
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #3438
            [FIX JENKINS-16827] Don't try to guess the build number (Revision b401cf1fbafe50b67d1ed4aebef5bf2909e662e3)

            Result = SUCCESS
            daniel-beck : b401cf1fbafe50b67d1ed4aebef5bf2909e662e3
            Files :

            • core/src/main/java/hudson/tasks/BuildTrigger.java
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #3438 [FIX JENKINS-16827] Don't try to guess the build number (Revision b401cf1fbafe50b67d1ed4aebef5bf2909e662e3) Result = SUCCESS daniel-beck : b401cf1fbafe50b67d1ed4aebef5bf2909e662e3 Files : core/src/main/java/hudson/tasks/BuildTrigger.java
            danielbeck Daniel Beck added a comment -

            Fixed by removing the guess (and it was nothing more) in 1.567.

            danielbeck Daniel Beck added a comment - Fixed by removing the guess (and it was nothing more) in 1.567.

            People

              danielbeck Daniel Beck
              l_roche Louis Roché
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: