Hi Glen,
I would of course keep the policy of not checking in code with test
failures. The indicator would even help
with this goal. Before checking in code you could look at the indicator
and only check in if it is green.
At the moment I can not see if the build is working. So if I check in my
code I can get a build failure that was not
caused by me. A build indicator would help with that.
Greetings
Christian
Glen Mazza schrieb:
Well, ideally of course, code should not be checked in with test failures.
Presence of such a build indicator on the web site might cause us to
wrongfully downgrade the importance of build failures, i.e., treat them as
we might open JIRA issues.
Incidentally, I also noticed build failures this weekend using Ubuntu Linux
(mvn clean install) so this may not just be a Windows issue.
Glen
Christian Schneider wrote:
Hi Dan,
I have got another idea. We should try to install a build indicator on
the CXF web site. It would be immensly helpfull if a developer could
see if the build
currently runs without failures on the integration test system.
Additionally we could have statistics showing how many unit tests fail
per module and in sum.
Perhaps these statistics and the overview information could be posted
during the build.
Of course it would also be great to provide read access to the
cruisecontrol system for all committers.
Greetings
Christian
--
Christian Schneider
---
http://www.liquid-reality.de
