On Jun 2, 2013 10:33 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > > So, the metric for success may require that script that checks for > > failures.txt and runs with the -failures options. > > Ok, that script is ready to go in 'jenkins.sh', it's commented out on > the bottom of the file. > > > But the interesting thing for me once we get this Jenkins thing running > > is: if several committers also set up this same Jenkins job, could we have > > them each run a subset of the mustella tests and report much sooner? I > > think it was you who suggested we could create a massively parallel > > mustella system. > > If only I was such a creative thinker. I won't take credit for that > idea as I don't have a clue where to start, even ;-) > > EdB > >
I have an Azure VM sitting idle. Theoretically, we could add it as a second slave and divvy up the Mustella run into two halves. We should be able to have a single run in half the time. The more slaves we can add, the faster the run would get. Do you want me to give this idea a shot? Thanks, Om
