Using svn you should be able to create a tag based on the revision you
retrieved when starting the build. This should solve your main problem
with option 2.
-Sven
On 1/21/07, Chris Polderman <chris.polderman@xxxxxxxxx> wrote:
Hello everyone,
I've just discovered Hudson a couple of weeks ago and I must say: I am
impressed; it is so easy to setup and manage! I dumped cruisecontrol
10 minutes after implementing hudson..
I initially started off using CVS but have successfully switched to
Subversion now.
Now for a quick question:
I want to setup the build process to do an automated tag on the last
stable build. I have a few options here:
1) use the ant script of the job to tag whenever a build completes successfully;
2) use the automated deployment (which is a downstream shellscript
style job) to do the tagging.
The main downside of option 2 is that the tag is placed a while after
the build of the upstream job finishes; this can cause the tag to be
placed on the wrong version on some files which have changed
inbetween.
Is option 1 the standard way to go?
Kind regards,
Chris Polderman
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxxxxx
| 