Thanks. Issue resolved On Monday, 3 March 2014 15:48:40 UTC+5:30, benjamin.a.lau wrote: > > I'm assuming all of these have the same parameters or are not > parameterized at all. Due to this the queue will be culled by Jenkins > such that only each unique job will appear in the queue. > > Marc MacIntyre (in the thread about for loops the other day) suggested > the following to compensate for this: > Depending on your job, you'll want to add some kind of bogus parameter > to the jobs to prohibit deduplication, since Jenkins can coalesce jobs > that are run with the same parameters in the queue. I use the current > system time in millis. > > That will probably solve your problem. > > Cheers, > Ben > > On Mon, Mar 3, 2014 at 1:32 AM, Jayaprakash D B > <[email protected]<javascript:>> > wrote: > > Hi, > > > > I have a project where we submit number of builds. As of now, I can see > only > > two jobs in the queue:one the running one and other the queued one. I > want > > to queue more than one job in a particular queue. Is it possible? > > > > Thanks, > > JP > > > > -- > > 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] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. >
-- 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.
