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

No up/downstream indication when using Parameterized Build Trigger plugin

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      (Copy of mail from Tim Arant on Hudson User list)

      I have noticed some issues related to Up-Stream and Down-Stream projects.

      Build other projects

      When this option is checked and a Down-Stream project is supplied, hyper-links appear on each related Project page that there is an Up-Stream or Down-Stream project associated with the Project being viewed,

      Trigger parameterized build on other projects

      When this option is checked and a Down-Stream project is supplied, no hyper-links appear on each related Project page. I realize that this is part of the Trigger plug-in, but it would be nice if this plug-in simply modified the existing "Build other projects" and allowed parameter definition, or, have this plug-in create the hyper-link relationships.

        Attachments

          Issue Links

            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
            dogfood dogfood added a comment -

            Integrated in plugins_parameterized-trigger #28
            [FIXED JENKINS-11082, FIXED JENKINS-9263, FIXED JENKINS-5184] Builds

            Andrew Bayer :
            Files :

            • src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
            Show
            dogfood dogfood added a comment - Integrated in plugins_parameterized-trigger #28 [FIXED JENKINS-11082, FIXED JENKINS-9263, FIXED JENKINS-5184] Builds Andrew Bayer : Files : src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
            Hide
            evernat evernat added a comment -

            committed so resolving as fixed, please reopen if needed

            Show
            evernat evernat added a comment - committed so resolving as fixed, please reopen if needed
            Hide
            mmacvicar Mark MacVicar added a comment -

            This issue is still occurring for us with Parameterized Trigger Plugin 2.17 and jenkins 1.504. The Downstream Build View plugin feature is able to see all the downstream jobs, but the job status page displays:

            Downstream Builds
            project_name(none)

            Show
            mmacvicar Mark MacVicar added a comment - This issue is still occurring for us with Parameterized Trigger Plugin 2.17 and jenkins 1.504. The Downstream Build View plugin feature is able to see all the downstream jobs, but the job status page displays: Downstream Builds project_name(none)
            Hide
            yangli907 Yang Li added a comment -

            Afte applied the Jenkins upgrade from v1.480 to v1.532.3, I found the concept of Jenkins Groovy API ‘getDownstreamProject()’ defined in AbstractProject class has been changed. In v1.480, all the post-build jobs and triggered jobs(using build trigger plugin) are treated as downstream job and will be retrieved by the API. However, in v1.532.1, only jobs triggered as post-build step is treated as downstream job.

            I want to know what's the proper API to use in order to get the triggered jobs information?

            Show
            yangli907 Yang Li added a comment - Afte applied the Jenkins upgrade from v1.480 to v1.532.3, I found the concept of Jenkins Groovy API ‘getDownstreamProject()’ defined in AbstractProject class has been changed. In v1.480, all the post-build jobs and triggered jobs(using build trigger plugin) are treated as downstream job and will be retrieved by the API. However, in v1.532.1, only jobs triggered as post-build step is treated as downstream job. I want to know what's the proper API to use in order to get the triggered jobs information?

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                ridesmet Ringo De Smet
              • Votes:
                7 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: