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

Downstream build view not working

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      linux: 2.6.31-20-server #58-Ubuntu SMP x86_64 + Java(TM) SE Runtime Environment (build 1.6.0_15-b03)

      Description

      the downstream build graph is ok, the problem is in job builds page where it knows which upstream build initialized this one, but when I go to that upstream build, it shows a list of downstream jobs with no build link ("none" instead).

      Also, this causes (I guess) "Downstream build view" to be an empty page.

      Similar problem is described here by SauravSengupta:
      http://n4.nabble.com/Downstream-build-view-not-working-tp1574056p1589711.html

      The jobs we use are mainly free style jobs connected in dependency hierarchy + matrix job (starting on exact time, instead of hierarchy). Hudson ver. 1.353.

        Activity

        Hide
        rakatan rakatan added a comment -

        forgot to mention

        the jobs use security per project. Not sure if this is related - since the problem exists both to read-only anonymous users and admin user.

        Show
        rakatan rakatan added a comment - forgot to mention the jobs use security per project. Not sure if this is related - since the problem exists both to read-only anonymous users and admin user.
        Hide
        jcarsique Julien Carsique added a comment -

        We have (none) for downstream Maven job but nothing at all (neither the job name) for Freestyle jobs.
        Downstream jobs have been triggered but don't appear in their parent's summary view

        Show
        jcarsique Julien Carsique added a comment - We have (none) for downstream Maven job but nothing at all (neither the job name) for Freestyle jobs. Downstream jobs have been triggered but don't appear in their parent's summary view
        Hide
        mmacvicar Mark MacVicar added a comment -

        I had a similar problem, it was caused by not using fingerprinting correctly to associate upstream/downstream jobs. I'm having difficulty finding documentation on the subject but this helped me http://stackoverflow.com/questions/17803165/does-jenkins-create-upstream-downstream-automatically.

        Show
        mmacvicar Mark MacVicar added a comment - I had a similar problem, it was caused by not using fingerprinting correctly to associate upstream/downstream jobs. I'm having difficulty finding documentation on the subject but this helped me http://stackoverflow.com/questions/17803165/does-jenkins-create-upstream-downstream-automatically .
        Hide
        danielbeck Daniel Beck added a comment -

        Is this still a problem in recent Jenkins versions? How can this be reproduced on a vanilla Jenkins instance? What is the expected result, what happens instead?

        Show
        danielbeck Daniel Beck added a comment - Is this still a problem in recent Jenkins versions? How can this be reproduced on a vanilla Jenkins instance? What is the expected result, what happens instead?
        Hide
        fastblitzer Christian Gnüchtel added a comment - - edited

        I can confirm this bug in recent Jenkins versions.

        Steps to reproduce on Windows (on other systems you have to replace the batch execution with shell execution):

        1. Download the latest jenkins.war and start it: java" -Xrs -Xmx512m -XX:MaxPermSize=128m -jar jenkins.war --httpPort=8081
        2. Copy the attached three job config.xml files zzz_a, zzz_b, zzz_c to the jobs directory. (The pipeline zzz_a -> zzz_b -> zzz_c.)

        http://localhost:8081/job/zzz_a/1/ displays:

        • Started by anonymous user
        • Downstream Builds zzz_b #1

        http://localhost:8081/job/zzz_b/1/ displays:

        • Started by upstream project zzz_a build number 1
        • originally caused by: Started by anonymous user
        • Upstream Builds zzz_a #1
        • Downstream Builds zzz_c (None)

        http://localhost:8081/job/zzz_c/1/ displays:

        • Started by upstream project zzz_b build number 1
        • originally caused by: Started by upstream project zzz_a build number 1, originally caused by: Started by anonymous user

        It does not display:

        • Upstream Builds

        Note, that the job pages

        In summary:

        • "Started by upstream project ..." texts are displayed correctly
        • Downstream builds are sometimes incorrectly displayed with "(none)"
        • If downstream builds are displayed incorrectly, upstream builds are incorrectly displayed too
        • Downstream jobs and upstream jobs are displayed correctly
        Show
        fastblitzer Christian Gnüchtel added a comment - - edited I can confirm this bug in recent Jenkins versions. Steps to reproduce on Windows (on other systems you have to replace the batch execution with shell execution): Download the latest jenkins.war and start it: java" -Xrs -Xmx512m -XX:MaxPermSize=128m -jar jenkins.war --httpPort=8081 Copy the attached three job config.xml files zzz_a, zzz_b, zzz_c to the jobs directory. (The pipeline zzz_a -> zzz_b -> zzz_c.) http://localhost:8081/job/zzz_a/1/ displays: Started by anonymous user Downstream Builds zzz_b #1 http://localhost:8081/job/zzz_b/1/ displays: Started by upstream project zzz_a build number 1 originally caused by: Started by anonymous user Upstream Builds zzz_a #1 Downstream Builds zzz_c (None) http://localhost:8081/job/zzz_c/1/ displays: Started by upstream project zzz_b build number 1 originally caused by: Started by upstream project zzz_a build number 1, originally caused by: Started by anonymous user It does not display: Upstream Builds Note, that the job pages http://localhost:8081/job/zzz_a/ http://localhost:8081/job/zzz_b/ http://localhost:8081/job/zzz_c/ display the upstream/downstream relationship correctly. In summary: "Started by upstream project ..." texts are displayed correctly Downstream builds are sometimes incorrectly displayed with "(none)" If downstream builds are displayed incorrectly, upstream builds are incorrectly displayed too Downstream jobs and upstream jobs are displayed correctly

          People

          • Assignee:
            Unassigned
            Reporter:
            rakatan rakatan
          • Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated: