> 20 minutes for AIR. > 82 minutes for mobile. > Add more for -failures runs if needed.
Ok, I'll add these 2 runs to jenkins.sh. Might be a good idea to keep the 'failures.txt' of each completed set (regular + -failures)? > I got a lot of bitmap failures that I'm looking into now. Which reminded > me that if a check-in goes bad and generates a lot of bitmap failures that > slows things down (all the bad pngs have to be written to disk). Is there > any way to set up jenkins to wait N minutes after a job completes before > starting the next job? What would happen if we run every 12 hours but > sometimes a job doesn't complete in those 12 hours? I don't think Jenkins will stop one job just to start it again because of a schedule... But I'll read up on it. The current run is 9 hrs, so adding 1.5 hrs still leaves us with plenty of room on 'reasonably clean' runs, right? EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
