Correction ... I cannot really use your workaround of a custom workspace because the build flow plugin does NOT show up the option of setting a workspace
On Friday, October 11, 2013 3:23:24 PM UTC+11, Neetish Jethra wrote: > > Hi Adam, > > I have been facing the same problem for our build and your workaround > works fine for normal builds and makes sure new builds are triggered via > SCM polling when a build is still in progress. > > However, I cannot get this workaround to work when I am using a Build > Flow project created using the Build Flow plugin ( > https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin). > > So, to summarize, my build flow project triggers a job that builds the > artefact that I want to test / deploy, followed by few parallel jobs that > test the artefact. If all of the parallel jobs work, I publish the artefact > to another repository to make it available for manual tesing (the publish > is done via a jenkins job as well). > > The orchestration of the jobs is done by the build flow project and it is > also responsible for git polling. > > I can see the same behaviour as mentioned by cjo, where the polling starts > but then gets stuck while the current job is still running. > > " > This might be a workspace locking issue as the polling log you post seems > to indicate that the polling has started [1], but has not completed. > even though the concurrent is allowed. > " > > I cannot really use your workaround of a custom workspace because the > build flow plugin does NOT show up the option of setting a workspace. From > what I understand, the Build Flow job uses a lightweight execution > environment and does not require any executors. > > Is there another way you can think of for achieving this . If you could > throw some light on how you arrived at the workaround, it might help me to > figure out a solution for my case. > > Thanks, > > Neetish. > > > > > > > > On Thursday, February 7, 2013 4:24:48 PM UTC+11, Adam Mercer wrote: >> >> On Mon, Jan 28, 2013 at 9:00 PM, Adam Mercer <[email protected]> wrote: >> >> > That sounds like a reasonable explanation. Is there a way I can have a >> > separate workspace for polling, so that this doesn't block? >> >> Just to close the loop on this, I set a custom workspace for this >> project and this allowed multiple jobs to be triggered. >> >> Cheers >> >> Adam >> > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
