+1
I use Hudson in my current assignment. Not only is it easy to automate
the builds, but you can see passing and failing unit tests and deltas
from the previous build. You also can see the commits that are
introduced into the build.
It's very easy for a developer or build captain or release manager to
track changes.
Adriano Crestani wrote:
I agree with Raymond, very good tool, very complete...good to keep track of
Tuscany progress
+1 : )
On Mon, May 11, 2009 at 4:17 PM, Raymond Feng <[email protected]> wrote:
+1.
I personally tried the Hudson. It's very rich in reports.
Thanks,
Raymond
--------------------------------------------------
From: "Luciano Resende" <[email protected]>
Sent: Monday, May 11, 2009 3:34 PM
To: <[email protected]>
Subject: Using Hudson zone for Tuscany Automated Builds
We have made various efforts to get our automated build build (see
last one [1]) going in the Apache Continnum environment (vmbuild1),
but it looks like we are always finding issues, etc, etc
I'd like to start experimenting with the Apache Hudson environment
[2], and have created a automated build for our 2.x code stream [3]
which is building OK after I workarounded an issue described in
TUSCANY-3015.
If people are ok with this move, I'll start exploring this more and
try to enabled :
- snapshot deployments
- build failure notifications
Then, once we are glad with the results, I'll apply the same for the
1.x code stream...
Thoughts ?
[1] http://www.mail-archive.com/[email protected]/msg04923.html
[2] http://hudson.zones.apache.org/hudson/
[3] http://hudson.zones.apache.org/hudson/job/Tuscany-2x/
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
http://lresende.blogspot.com/
--
Thanks, Dan
email: mailto://[email protected]
