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

Downstream Build View does not recognize parameterized build trigger

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I have four jobs:
      />DOWNSTREAM1>\
      UPSTREAM->| |->JOIN
      ->DOWNSTREAM2->/

      If I configure UPSTREAM to trigger the two downstream jobs using "Build other projects", they show up in the downstream view.
      If I trigger them with "Trigger parameterized build on other projects" however, they don't.

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Andrew Bayer
          Path:
          src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
          http://jenkins-ci.org/commit/parameterized-trigger-plugin/a23dfab2775e2ffb84d5aa73da4533e971c690cb
          Log:
          [FIXED JENKINS-11082, FIXED JENKINS-9263, FIXED JENKINS-5184] Builds
          triggered as build steps will now show up in the dependency graph.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrew Bayer Path: src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/a23dfab2775e2ffb84d5aa73da4533e971c690cb Log: [FIXED JENKINS-11082, FIXED JENKINS-9263, FIXED JENKINS-5184] Builds triggered as build steps will now show up in the dependency graph.
          Hide
          miktap Mikko Tapaninen added a comment -

          It's still not working properly. I tested with Parameterized Trigger plugin 2.13 and Downstream buildview plugin at revision https://github.com/jenkinsci/downstream-buildview-plugin/commit/9ce09015e02e371420c40a759c764adf830afd76.

          If builds are triggered in post-build phase, then downstream view looks good. But if builds are triggered as build step, then downstream view does not get any information (build number, build status) back from the called downstream build.

          Show
          miktap Mikko Tapaninen added a comment - It's still not working properly. I tested with Parameterized Trigger plugin 2.13 and Downstream buildview plugin at revision https://github.com/jenkinsci/downstream-buildview-plugin/commit/9ce09015e02e371420c40a759c764adf830afd76 . If builds are triggered in post-build phase, then downstream view looks good. But if builds are triggered as build step, then downstream view does not get any information (build number, build status) back from the called downstream build.
          Hide
          wsoula will soula added a comment -

          Sometimes it works and sometimes it doesn't and it appears to be based on whether or not the “Block until the triggered projects finish their builds” checkbox is checked or not:

          Steps to Reproduce:
          Install the Downstream Build View plugin and the Parameterized Trigger plugin
          Create a new job, jobA, and under Build select Trigger/call builds on other projects
          Under Projects to build enter jobB (I know it doesn’t exist yet but we are about to create it)
          Create a new job, jobB, and don’t configure it further
          Kick off a build of jobA and then click that build and click the Downstream build view link and notice jobB build number 1 is shown
          Go back to jobA and click the checkbox under the Build section “Block until the triggered projects finish their builds”, then click save
          Kick off a build of jobA and then click that build and click the Downstream build view link and notice jobB build number 2 is not shown and instead it says jobB is NOT_BUILT

          Versions:
          Jenkins – 1.470
          Downstream build view – 1.7
          Jenkins Parameterized Trigger plugin – 2.15
          Plugins installed but Jenkins not restarted since apparently you can now install plugins without restarting

          Show
          wsoula will soula added a comment - Sometimes it works and sometimes it doesn't and it appears to be based on whether or not the “Block until the triggered projects finish their builds” checkbox is checked or not: Steps to Reproduce: Install the Downstream Build View plugin and the Parameterized Trigger plugin Create a new job, jobA, and under Build select Trigger/call builds on other projects Under Projects to build enter jobB (I know it doesn’t exist yet but we are about to create it) Create a new job, jobB, and don’t configure it further Kick off a build of jobA and then click that build and click the Downstream build view link and notice jobB build number 1 is shown Go back to jobA and click the checkbox under the Build section “Block until the triggered projects finish their builds”, then click save Kick off a build of jobA and then click that build and click the Downstream build view link and notice jobB build number 2 is not shown and instead it says jobB is NOT_BUILT Versions: Jenkins – 1.470 Downstream build view – 1.7 Jenkins Parameterized Trigger plugin – 2.15 Plugins installed but Jenkins not restarted since apparently you can now install plugins without restarting
          Show
          viglesias Vic Iglesias added a comment - There are currently 2 pull requests that fix this issue: https://github.com/jenkinsci/downstream-buildview-plugin/pull/3 https://github.com/jenkinsci/downstream-buildview-plugin/pull/2
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Vic Iglesias
          Path:
          src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewRunListener.java
          http://jenkins-ci.org/commit/downstream-buildview-plugin/c653ce3ebf2b9a0ba5c91a942fb80931ba80d9a2
          Log:
          Add downstreamBuildViewAction to upstream build when downstream build is started instead of compeleted
          FIXES: JENKINS-9263
          https://issues.jenkins-ci.org/browse/JENKINS-9263

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Vic Iglesias Path: src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewRunListener.java http://jenkins-ci.org/commit/downstream-buildview-plugin/c653ce3ebf2b9a0ba5c91a942fb80931ba80d9a2 Log: Add downstreamBuildViewAction to upstream build when downstream build is started instead of compeleted FIXES: JENKINS-9263 https://issues.jenkins-ci.org/browse/JENKINS-9263
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Nicolas De loof
          Path:
          src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewRunListener.java
          http://jenkins-ci.org/commit/downstream-buildview-plugin/60f60144dc235cfe6d4c01959c0dc0043c715e7f
          Log:
          Merge pull request #3 from viglesiasce/master

          FIXES: JENKINS-9263

          Compare: https://github.com/jenkinsci/downstream-buildview-plugin/compare/85fe4cd24e74...60f60144dc23

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jvnet/hudson/plugins/DownstreamBuildViewRunListener.java http://jenkins-ci.org/commit/downstream-buildview-plugin/60f60144dc235cfe6d4c01959c0dc0043c715e7f Log: Merge pull request #3 from viglesiasce/master FIXES: JENKINS-9263 Compare: https://github.com/jenkinsci/downstream-buildview-plugin/compare/85fe4cd24e74...60f60144dc23
          Hide
          ikedam ikedam added a comment -

          This seems already fixed with changes by Vic.
          Please reopen this if problems remain.

          Show
          ikedam ikedam added a comment - This seems already fixed with changes by Vic. Please reopen this if problems remain.

            People

            • Assignee:
              shinodkm shinodkm
              Reporter:
              voorth voorth
            • Votes:
              10 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: