I think I've found a solution in the form of the Lockable Resources plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Lockable+Resources+Plugin Thanks. Phil. On Friday, 19 February 2016 11:39:31 UTC, Philip Pemberton wrote: > > Hi, > > I've been given the job of automating the build of some new-ish code for a > crusty old system which uses a cranky old build system which depends on > hard-coded paths. Essentially, all input source files must be in the same > directory, my build script has to copy the source into that directory from > the Jenkins workspace, then the outputs it produces are zipped and archived. > > Sadly I have two independent projects which depend in this little horror > of a compiler. > > If someone runs a build for Project A, and Project B's scheduled build > happens to start just after, one (or both) of the two builds will fail. > > I've tried creating a parent project which polls the SCM and kicks off > Project A and Project B, then set both "Block build when upstream project > is building" and "Block build when downstream project is building" on A > and B, but this doesn't have the desired effect (A and B end up stomping on > each other). > > How can I do this with Jenkins? > > Thanks, > Phil. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3823acae-426e-4aed-9e71-8b1c80472ead%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
