On 29/08/2007, at 7:48 PM, Emmanuel Venisse wrote:
2) rebuild a project that was in error state before.
I think it's the best solution for now and won't be a lot of work.
agreed... can we sneak this into the 1.1 JIRA? :D
Only the first would also address the problem of having
difficulties diagnosing errors that occur even earlier and don't
record a build result at all. It also is a nice separation of
configuration/environmental errors vs actual build failures. It
helps with the separation of roles when you have a server admin
and developers that just commit on the code.
However, it's a lot more work, and it might be better to schedule
that for the future and fix it via (2) for 1.1.
I'm agree even if I don't know yet how to find the error type.
Anything that can set an error state on the project needs to be
reviewed to make sure it records a build result if it doesn't already
- I've definitely found some that don't (eg, missing POM parent after
scm update)
- Brett
