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

Problems when running the batch task in parallel with the main job




      I am using the Batch Task plugin to perform releases for my Hudson jobs. But every once in a while, Hudson would start the real job in parallel with the release task, and almost always, this leads to failed builds with very odd behaviors.

      I am using a high frequency for checking CVS changes, about once every 15 minutes (I should change this, but that is a different problem), and when the release task checks in the updated POM into CVS, then this shows up as a code change, and Hudson would start the main job, even though the batch task is not done yet.

      To prevent this issue, I have to disable the main job when I start a batch task to prevent the race condition, and once the release is complete, I enable the job again. The problem is that I often forget this.

      It would be real nice if Hudson or the Batch task can use a form of a lock for the workspace to ensure that only one job/batch can execute at a given time.



          fshehadeh fshehadeh created issue -
          mindless Alan Harder made changes -
          Field Original Value New Value
          Assignee kohsuke [ kohsuke ] mindless [ mindless ]
          mindless Alan Harder made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          scm_issue_link SCM/JIRA link daemon made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 135374 ] JNJira + In-Review [ 203443 ]


            mindless Alan Harder
            fshehadeh fshehadeh
            0 Vote for this issue
            2 Start watching this issue