I agree that our builds have not been at all reliable lately. I've noticed three categories of problem:
1. Svn failures. Since the upgrade to Jenkins 1.40 (I think), the svn update sometimes fails and we build against an old revision of the Aries code bade. I've raised https://issues.apache.org/jira/browse/INFRA-4949 to cover the issue. I wondered if changing the build to do a complete checkout rather than update would fix this. The downside is it would slow the builds down. 2. Jenkins IO failures. 3. Intermittent failures in EJB and quiesce tests. I think this is minor compared to 1. and 2. The latest batch of failures seem to be a mix of weird Jenkins exceptions and weird intermittent test failures, which I have no bright ideas for fixing, unfortunately. On Thu, Jul 12, 2012 at 3:18 PM, Emily Jiang <[email protected]> wrote: > I experienced a few times that Jenkins failed for no apparent reason and > then back to stable without any fix going in. Hence, someone could waste > time to debug a non-existing problem. Is there anything we can do to > improve its behaviour? > > -- > Thanks > Emily > ================= > Emily Jiang > [email protected]
