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

Projects specified in "Trigger parameterized build on other projects" are triggered twice

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Downstream parametrized triggered job are triggered twice.

      See also: http://n4.nabble.com/Problems-with-new-release-of-Parametrized-trigger-plugin-td1010656.html#a1010656

        Attachments

          Activity

          Hide
          mindless Alan Harder added a comment -

          r25700 | mindless | 2010-01-11 18:01:03 -0700 (Mon, 11 Jan 2010)
          Changed paths:
          M /trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java

          [FIXED JENKINS-5232] comment out DependencyDeclarer stuff from r20598,
          as this causes Hudson to trigger builds twice (once with params from our perform(),
          once w/o params from core's BuildTrigger.execute).
          Also remove readResolve with just a System.out.println.

          Show
          mindless Alan Harder added a comment - r25700 | mindless | 2010-01-11 18:01:03 -0700 (Mon, 11 Jan 2010) Changed paths: M /trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java [FIXED JENKINS-5232] comment out DependencyDeclarer stuff from r20598, as this causes Hudson to trigger builds twice (once with params from our perform(), once w/o params from core's BuildTrigger.execute). Also remove readResolve with just a System.out.println.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java
          http://fisheye4.cenqua.com/changelog/hudson/?cs=25700
          Log:
          [FIXED JENKINS-5232] comment out DependencyDeclarer stuff from r20598,
          as this causes Hudson to trigger builds twice (once with params from our perform(),
          once w/o params from core's BuildTrigger.execute).
          Also remove readResolve with just a System.out.println.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/plugins/parameterized-trigger/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java http://fisheye4.cenqua.com/changelog/hudson/?cs=25700 Log: [FIXED JENKINS-5232] comment out DependencyDeclarer stuff from r20598, as this causes Hudson to trigger builds twice (once with params from our perform(), once w/o params from core's BuildTrigger.execute). Also remove readResolve with just a System.out.println.
          Hide
          emmulator emmulator added a comment -

          I've got the Parametrized Trigger Plugin version 2.1 and Hudson 1.339. My build triggered by the plugin last night ran twice and ingnored the parameter values that should be coming from the triggering Job, using instead the defaults defined on the triggered Job.

          I tested it again today by setting up a simple Job that just prints the 'env' and then calls the Triggered Parameterized Job. The Job was indeed scheduled twice and did not use the values I set in the Parameters.

          Show
          emmulator emmulator added a comment - I've got the Parametrized Trigger Plugin version 2.1 and Hudson 1.339. My build triggered by the plugin last night ran twice and ingnored the parameter values that should be coming from the triggering Job, using instead the defaults defined on the triggered Job. I tested it again today by setting up a simple Job that just prints the 'env' and then calls the Triggered Parameterized Job. The Job was indeed scheduled twice and did not use the values I set in the Parameters.
          Hide
          emmulator emmulator added a comment -

          Sorry, I misunderstood what version this was supposed to apply to (the "Affects Version/s:" and "Fix Version/s:" are still blank...) I've got the newer 2.2 now, and my Jobs are only triggered once.

          Show
          emmulator emmulator added a comment - Sorry, I misunderstood what version this was supposed to apply to (the "Affects Version/s:" and "Fix Version/s:" are still blank...) I've got the newer 2.2 now, and my Jobs are only triggered once.
          Hide
          emmulator emmulator added a comment -

          Resetting back to resolved/fixed

          Show
          emmulator emmulator added a comment - Resetting back to resolved/fixed

            People

            • Assignee:
              mindless Alan Harder
              Reporter:
              kutzi kutzi
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: