3

I have a build that polls SVN and checks for changes every hour. if it finds changes it starts building.

Right now if it sees changes and a previous build (from the same job) is running, it will queue the build and start it when the previous build finishes.

Is there an option to disable the queuing of multiple builds ?

Michael
  • 22,196
  • 33
  • 132
  • 187

1 Answers1

1

Here's a workaround: let one job (Trigger) do the polling and then call the main job (MainJob) that will do the updating and building. You can even use the Parameterized Trigger Plugin to pass the SVN revisions and URIs. You then check off Block build when downstream project is building in Trigger.

To propagate change-sets from Trigger to MainJob use BlameSubversion Plugin.

(BTW, here's a neat trick: Trigger does not have to check out the whole SVN tree, you can check it out by hand with --set-depth empty in the working copy of Trigger).

malenkiy_scot
  • 16,415
  • 6
  • 64
  • 87
  • 1
    Nice workaround. I just find it hard to accept that there isn't an option or plugin that will let me disable queuing builds. it sounds like something very basic. – Michael Mar 19 '12 at 11:31
  • I agree. You already have "block when upstream/downstream job building", why not to have "block when this job is building"? Maybe there is an easy way out that I'm missing. – malenkiy_scot Mar 19 '12 at 14:42