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

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

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • None
    • Parametrized Trigger plugin 2.1

      Downstream parametrized triggered job are triggered twice.

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

          [JENKINS-5232] Projects specified in "Trigger parameterized build on other projects" are triggered twice

          kutzi created issue -
          Alan Harder made changes -
          Assignee Original: huybrechts [ huybrechts ] New: Alan Harder [ 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.

          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.
          Alan Harder made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          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.

          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.

          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.

          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.
          emmulator made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          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.

          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.

          emmulator added a comment -

          Resetting back to resolved/fixed

          emmulator added a comment - Resetting back to resolved/fixed
          emmulator made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]

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

              Created:
              Updated:
              Resolved: