Hi,
As being discussed on the other thread, we all agree that it's very
important to keep the trunk build successfully all the time. There are
different factors that contribute to the build breaks:
1) Changes are checked in without a full clean build before the commit
We should always try to run a full build before we check in the changes.
Don't assume one line of change is safe :-).
2) Some files are missing from the commit (for example, forget to select the
new files...)
Mistakes can happen and we should pay more attentions. Some svn tools can
help. For example, run "svn stat" to see if some files are missed after the
commit. The key is to get notified if the break happens and try to fix it
ASAP.
3) Some intermittent errors
This is tricky. It can be timing issue, environment issue. We can disable
the test with @Ignore("JIRA#") pattern while we investigate.
4) Code behaviors that are OS or JDK specific
This is tricky. By my experience, some of the issues lay in our code, for
example, Linux may give us a different order for the file list in a jar or
entries in a map. Reproduce the problem and debug often reveal bugs in our
code (such as conflicting artifacts). Others may be related to some JDK
bugs.
Thanks,
Raymond
