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

Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"

XMLWordPrintable

    • Icon: Patch Patch
    • Resolution: Unresolved
    • Icon: Major Major
    • downstream-buildview-plugin
    • None
    • Hudson (version 1.347)
      Parameterized Trigger plugin (version 2.3)
      Downstream build view (version 1.4)

      I am experiancing trouble with the "Downstream-Ext" and "Parametrized Build" plugins:

      • I have a parent job which has one (or more) downstream jobs triggered with the "Parameterized Trigger plugin".
      • I run the parent job which triggers the child with the correct parameters, but when I then look at the downstream view for the parent job run, there is nothing shown.
      • If I do the same with the childs being configured as normal "build other project", then I see all the child builds in the downstream view.

        1. downstream-buildview.hpi
          21 kB
        2. downstream-buildview.diff
          3 kB
        3. downstream_parambuild_issue.png
          downstream_parambuild_issue.png
          49 kB

          [JENKINS-5761] Projects triggered by "Parameterized Build Plugin" do not show in view with "Downstream-buildview"

          illenseer created issue -

          kutzi added a comment -

          If I've understood your description correctly, this has nothing to do with the downstream-ext plugin, but only with the parametrized trigger!?

          kutzi added a comment - If I've understood your description correctly, this has nothing to do with the downstream-ext plugin, but only with the parametrized trigger!?

          illenseer added a comment - - edited

          I do not know, who is responsible or which plugin is causing this effect, that is why I chose both plugins as affected components. (Then JIRA automatically assigned the issue to you, Christoph [kutzi].)

          I wanted to show that it obviously is the combination of both plugins not producing the expected output.

          So Christoph: If you have the opinion that it's the "Parameterized Trigger plugin" which causes this, please feel free to change the assignee to Tom [huybrechts].

          illenseer added a comment - - edited I do not know, who is responsible or which plugin is causing this effect, that is why I chose both plugins as affected components. (Then JIRA automatically assigned the issue to you, Christoph [kutzi] .) I wanted to show that it obviously is the combination of both plugins not producing the expected output. So Christoph: If you have the opinion that it's the "Parameterized Trigger plugin" which causes this, please feel free to change the assignee to Tom [huybrechts] .

          kutzi added a comment -

          Assigning to parameterized-trigger component only.
          And BTW my name is Christoph, that's at least what my ID card said the last time I checked it.

          kutzi added a comment - Assigning to parameterized-trigger component only. And BTW my name is Christoph, that's at least what my ID card said the last time I checked it.
          kutzi made changes -
          Component/s Original: downstream-ext [ 15682 ]
          Assignee Original: kutzi [ kutzi ] New: huybrechts [ huybrechts ]

          illenseer added a comment -

          And BTW my name is Christoph, that's at least what my ID card said the last time I checked it.

          SORRY! - I was doing too many things in parallel and mixed-up your name! (I corrected the above comment accordingly.)

          illenseer added a comment - And BTW my name is Christoph, that's at least what my ID card said the last time I checked it. SORRY! - I was doing too many things in parallel and mixed-up your name! (I corrected the above comment accordingly.)
          mdonohue made changes -
          Link New: This issue depends on JENKINS-5184 [ JENKINS-5184 ]

          mdonohue added a comment -

          My understanding of JENKINS-5184 is that parameterized-trigger now contributes to the core dependency graph. If that's true, then perhaps downstream-ext isn't looking at the right datastructures to generate the report.

          mdonohue added a comment - My understanding of JENKINS-5184 is that parameterized-trigger now contributes to the core dependency graph. If that's true, then perhaps downstream-ext isn't looking at the right datastructures to generate the report.
          mdonohue made changes -
          Component/s New: downstream-ext [ 15682 ]

          kutzi added a comment -

          mdonohue: if I understand the problem report right, the user isn't even using the downstream-ext trigger for this job.
          BTW: What report are you talking about? Downstream-ext doesn't create any reports.

          ilenseer: have you checked the 'Build other projects (extended)' section in your build config? If not, you're not using downstream-ext for this job.

          kutzi added a comment - mdonohue: if I understand the problem report right, the user isn't even using the downstream-ext trigger for this job. BTW: What report are you talking about? Downstream-ext doesn't create any reports. ilenseer: have you checked the 'Build other projects (extended)' section in your build config? If not, you're not using downstream-ext for this job.

            huybrechts huybrechts
            illenseer illenseer
            Votes:
            11 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: