To be honest, I ignore Jenkins emails.
My experience shows me that 95% of these problems are problems of
hudson build(s)/environment/... or problems which I'm already
Instead of rely on the hudson builds I regularly run tycho build
locally. It safes our time. So instead of investigating what is
going on with hudson builds every time I got Jenkis email we
(CDI/Seam/JSF team) can spend time on development running local
tycho build every other day to make sure everything is ok on our
We mentioned these problems in JIRA and in emails but the hudson
builds is still unstable.
On 08/29/2012 11:58 PM, Mickael Istria wrote:
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" section.
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.
jbosstools-dev mailing list