Any input/advice on this issue?
On Monday, October 22, 2012 9:07:00 AM UTC+2, Hendrik Meiring wrote: > > Hi, > > We have been using Jenkins/hudson for a couple of years and I have now > converted my build project to make use of the concurrent launching of > projects. > In short we have a couple of projects that must be compiled on four > different os/architectures. > > *Node Setup* - unchanged from previous working setup. > Four dumb slaves running on four different VM's with the number of > executors set to 1. Their names are devel-win32, devel-win64, devel-lin32 > and devel-lin64. > > *Job setup* > The job is set up as a 'Build multi-configuration project' with the 'The > build is parameterized' option checked. The parameterized section contains > a Node parameter with my 4 nodes specified as possible nodes. > The 'Allow multi node selection for concurrent builds ' option is > selected and the 'Execute concurrent builds if necessary' is selected. > > I am aware of https://issues.jenkins-ci.org/browse/JENKINS-15370 that > make concurrent build triggering using multi-selection not an option for me > but now I am experiencing the following with the above setup: > > When I manually trigger the above job (single) selecting a different > platform/node each time the builds are correctly triggered and appears to > be running underneath the appropriate node on the left hand panel but after > more detailed investigating I found that one of the jobs are building and > the other jobs are blocked on the other machines until the job that is busy > are completed - thus sequential building...... grrr > > Am I missing something here? > > Thanks in advance > Hendrik >
