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

Overlapping parameterized builds gets confused on downstream jobs

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Hudson 1.372, ext-email, join, other basic plug-ins

      We run job 'ONE' that calls parameterized jobs "A","B","C" and "D" with a join job
      We have another job 'TWO' that also calls jobs "A" and "B" with a different join job. (Maybe not the best idea, but it seemed a good one at the time.)

      Let's say job TWO is started and triggers job A (build 129) and job B (build 122)
      Before job A and job B are finished, someone starts job ONE.

      Job ONE starts job A (build 130) and job B (build 123) correctly, along with jobs C and D.
      In the log of job ONE it reports it started job A #129 and job B #122 instead of the correct job numbers. (Now I haven't tried to figure out if "join" gets confused by all of this, but the possibility is there.)

      Here are some cut and paste from the logs:
      [cwrt-trunk-WST-MMO-try] Build 17: (JOB TWO)
      Triggering a new build of cwrt-trunk-HARVEY-MMO-arm-try #129
      Triggering a new build of cwrt-trunk-HARVEY-MMO-i486-try #122

      [cwrt-trunk-WST-all-try] Build 982: (JOB ONE)
      Triggering a new build of cwrt-trunk-HARVEY-MMO-arm-try #129
      Triggering a new build of cwrt-trunk-HARVEY-MMO-i486-try #122
      Triggering a new build of cwrt-trunk-linux-LNX-try #227
      Triggering a new build of cwrt-trunk-tb101_BANGER-Win-WST-try #152
      -----------------

          [JENKINS-7557] Overlapping parameterized builds gets confused on downstream jobs

          Chris Engel added a comment -

          I believe I'm having similar issues with Jenkins 1.579 parameterized plugin 2.26 and think it is related to the join job and using the 'parameters from file' option.

          I have all parameterized jobs A, B, C, D. A kicks off jobs B,C and then job D on completion of B and C with the join plugin.

          If I run the job cycle once everything runs fine, however if I have multiple in parallel I have issues.

          So if job A (build 1) is run in the process it creates a file in the job A workspace with parameters for jobs B&C (builds 1), it then initiates jobs B,C (builds 1) which correctly take the parameters created by job A build 1

          Then while B,C (build1) are still running job A (build 2) is run it can reuse the Jenkins workspace from build 1 and overlay with a new file with parameters for jobs B,C (builds 2) and then initiates jobs B,C (builds2)

          Now when Jobs B,C (build1) complete the join plugin kicks in to run job D for build1, however it appears it is rereading the parameters file from the Jenkins workspace which has been overlayed by job A build 2 such that job D for build1 will get parameters for build 2 and job D as configured for build 1 will never be run.

          Chris Engel added a comment - I believe I'm having similar issues with Jenkins 1.579 parameterized plugin 2.26 and think it is related to the join job and using the 'parameters from file' option. I have all parameterized jobs A, B, C, D. A kicks off jobs B,C and then job D on completion of B and C with the join plugin. If I run the job cycle once everything runs fine, however if I have multiple in parallel I have issues. So if job A (build 1) is run in the process it creates a file in the job A workspace with parameters for jobs B&C (builds 1), it then initiates jobs B,C (builds 1) which correctly take the parameters created by job A build 1 Then while B,C (build1) are still running job A (build 2) is run it can reuse the Jenkins workspace from build 1 and overlay with a new file with parameters for jobs B,C (builds 2) and then initiates jobs B,C (builds2) Now when Jobs B,C (build1) complete the join plugin kicks in to run job D for build1, however it appears it is rereading the parameters file from the Jenkins workspace which has been overlayed by job A build 2 such that job D for build1 will get parameters for build 2 and job D as configured for build 1 will never be run.

            huybrechts huybrechts
            markjwolff markjwolff
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: