This is a warning since we plan a code freeze for tomorrow: a lot of
jobs are failing (timeout, or just compilation or assembling issue, or
Jenkins configuration). As developers on a component, you must react to
a build becoming red, so don't ignore Jenkins mail notifications, read
the log when a build fails and*fix it ASAP*, if you can. You may be
interested in receiving mails specifically for your component, so you
can add you mail address on the Configuration page, "Mail notifications"
In some cases, log is explicit and shows what file crashed the build. So
you can guess what you need to do to fix it.
In other cases, it is be an environment issue, then open a ticket to the
Build/Releng component and assign it to Nick or I depending on your
timezone, so we can help to get the job back to work.
Since we are moving to bigger components, with more isolation, you
really need to be careful about the status of your component CI job.
Please don't wait for QE or Build crew to discover issues and fix it, it
simply won't scale.
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com>
- My Tweets