That is fine, I can set it up without the tagging. I have set this up on 5 projects so far though and the tagging is not really unweildy. We are on 1.2.186 currently. We then increment the 2 to a 3 and start back at 1 as in 1.3.1 and start all over. We have been getting about 180 builds every release.
Developers,
*****You will only receive an e-mail if you check something in.****. Will the e-mails within an hour of checking in bother anybody else? I want to receive a few more responses before I take any action. You will not receive it if another developer checks something in. You can always let me set it up and try it and tell me to turn it off. I just don't want to annoy anybody.
thanks for your support,
Dean
Keith Visco wrote:
Hi Dean, See inline...Dean Hiller wrote:Developers, Would this be opposed or welcomed..... I have automated many, many builds at my company with a tool that hooks into Ant. I would like to do the same with castor now that I am using it. Basically, it checks for any repository activity in the last hour and if there is any new checkins, it compiles, runs the JUnit tests, posts the results to a webserver and mails only the people that made checkins in the last hour so they know they were successful or if they broke the build at which point they can go back and fix the bugs they introduced. Rule in my department is you can't go home until you see the build successful e-mail. It automatically increases the build number AND tags CVS, so there is not manual work anymore. Would this be opposed or welcomed?????You are more than welcomed to automate a build on a per-checkin basis, or nightly basis, to make sure the CVS compiles and passes the test cases, however tagging the CVS and incrementing the build number everytime someone does a checkin, or on a nightly basis is not desired. The amount of CVS tagging would become unwieldy. We manually handle incrememting the build number when we are ready to do a release, the CVS can be automatically tagged with the ANT build script when we do the release. Thanks, --Keith ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
