Had a look at it. I think I did look at it at the time but didn't work for 
us then. Not sure if there is more info in the wiki as its down. From my 
brief play I like some bits of it but others not so much. 

   - I kinda like the separate sub job thing but could be confusing to 
   people
   - No easy way to tell where a particular test ran, ie which server, so 
   if it breaks you don't know where to go looking for extra info or which 
   build log to look at for a php fatal error backtrace
   - The way it excludes tests is both a positive and a negative to me 
   would prefer the parent discovered all tests and included in the sub, but I 
   know that's not always an option, so maybe an option to do either. Can see 
   this being a problem for php projects as unit tests could fail from the 
   same test running against the same DB at the same time if it didn't see a 
   particular test in the last run (which happens to us on a regular basis 
   when someone introduces a fatal error)
   - It splits up the tasks at the start vs handing them out as the last 
   one completes so if one test takes a lot longer than normal it holds up the 
   others

Is there a nice way to pass repo vers etc down now? I spent ages looking at 
the code and the way I ended up doing it always felt a bit hacky

On Friday, July 31, 2015 at 2:35:41 AM UTC+9:30, Jesse Glick wrote:
>
> On Thu, Jul 23, 2015 at 8:18 PM, David van Laatum <[email protected] 
> <javascript:>> wrote: 
> > The problem we had with the existing jenkins stuff was that it was hard 
> to 
> > split up the unit tests using the matrix plugin into equal runtime 
> groups 
>
> You can use the Parallel Test Executor plugin for this, with a 
> freestyle project or Workflow, e.g. 
>
>
> https://github.com/jenkinsci/parallel-test-executor-plugin/blob/7bdb270ffe02838a36f56d4de16ebe61cd3a9556/demo/JENKINS_HOME/jobs/flow/config.xml#L12
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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-dev/8cec2792-9260-4434-b61b-4f655b05e2c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to