I've changed the job schedule to every 10 hours, no matter what; it
was set to check the SCM every 10 hours and run when changes where
submitted. That makes sense when all is well, but for the first few
weeks I'd like to see it run cleanly twice a day and figure out if the
machine and the code
On Mon, Jun 17, 2013 at 12:57 AM, Erik de Bruin e...@ixsoftware.nl wrote:
I've changed the job schedule to every 10 hours, no matter what; it
was set to check the SCM every 10 hours and run when changes where
submitted. That makes sense when all is well, but for the first few
weeks I'd like
See http://localhost:8080/job/flex-sdk_mustella/171/changes
Changes:
[bigosmallm] Mustella -failures now works on Jenkins, so enable the full run
--
[...truncated 82850 lines...]
[loadfile]
Hey! We're essentially done! It looks like I forgot to push a change that
fixes the one remaining failure, but unfortunately, that change is sitting
on a computer that I won't see until Tuesday at the earliest.
I think this is currently in a good enough state to put on a regular
schedule. If
