Jason van Zyl wrote:
What is going on here? I fixed this code almost two days ago.
http://jakarta.apache.org/builds/gump/2001-05-21/cvs_index.html
http://jakarta.apache.org/builds/gump/2001-05-22/cvs_index.html
Compare this to the good old days:
Tim Vernum wrote:
In general, I believe that automated build/test processes are *very*
important, an do work.
We've got some teams using CruiseControl here, and it is doing well.
The reasons I think that gump registers so many failures are:
1) The environment in which gump runs is not
Geir Magnusson Jr. wrote:
There is nothing (other than the sloth of Daedalus) which prevents us
from adding any 'test' we want - Gump is running the Velocity testbed,
for example, which is more than interface-related, but functional as
well.
That test suite takes 58 seconds to run. I think
3) Developers can't/don't test other projects.
This is particularly relevant to ant, but also to some of the XML
and (soon) commons modules.
A number of build failures have been due to changes in ant.
Ant should continue to be free to change things as needed to make
Sam Ruby wrote:
Geir Magnusson Jr. wrote:
There is nothing (other than the sloth of Daedalus) which prevents us
from adding any 'test' we want - Gump is running the Velocity testbed,
for example, which is more than interface-related, but functional as
well.
That test suite takes