Yes, To participate in the CruiseControl mailing list you need to subscribe...just like this ANT mailing list Please visit the CruiseControl main page (at http://cruisecontrol.sourceforge.net/) and follow the Mailing List link (from the left side) and subscribe to the User Mailing list. As I had asked once before please don't add my personal email address onto an email that is sent to the ANT user group, this results in me recieving duplicate emails (as I already a receipent of group emails) and everyone replies are also sent to me!!! As I had asked you once already, I now consider your behavior quite rude. Guidelines on internet mail group equittte: http://jakarta.apache.org/site/mail.html and http://www.catb.org/~esr/faqs/smart-questions.html
----- Original Message ---- From: [EMAIL PROTECTED] To: [email protected]; [EMAIL PROTECTED] Sent: Friday, February 17, 2006 5:01:03 PM Subject: RE: Regarding Continous build integration. Do I need to register to send emails to this mailing list.? Thanks srikrishna -----Original Message----- From: Ninju Bohra [mailto:[EMAIL PROTECTED] Sent: Friday, February 17, 2006 5:55 PM To: Ant Users List Subject: Re: Regarding Continous build integration. I believe you have sent this email to the wrong mailing list...this the ANT user's mailing. Your question is more directed to the CruiseControl user list ([EMAIL PROTECTED]) Try again, Ninju ----- Original Message ---- From: [EMAIL PROTECTED] To: [email protected] Sent: Friday, February 17, 2006 4:52:25 PM Subject: RE: Regarding Continous build integration. I have multiple projects for which I want to use cruisecontrol to do builds. What is the best way to configure this.? I have c:\ cvssource Checkout/project1 Checkout/project2 Log/project1 Log/project2 Artifact/project1 Artifact/project2 <cruisecontrol> <project name="MY_PROJECT_1" buildafterfailed="true"> <!-- Bootstrappers are run every time the build runs, *before* the modification checks <bootstrappers> <currentbuildstatusbootstrapper file="logs/project1/buildstatus.txt"/> </bootstrappers> --> <!-- Defines where cruise looks for changes, to decide whether to run the build --> <modificationset quietperiod="10"> <cvs localworkingcopy="checkout/project1/jinxweb"/> </modificationset> <!-- Configures the actual build loop, how often and which build file/target --> <schedule interval="60"> <ant antscript="C:\ apache-ant-1.6.2\ bin\ ant.bat" buildfile="cc-build.xml" target="build" uselogger="true" usedebug="true"/> </schedule> <!-- directory to write build logs to --> <log dir="logs/project1"/> <!-- more recent versions of CC should use the listener below, instead of the currentbuildstatusbootstrapper, currentbuildstatuspublisher combination. NOTE: Must match filename in CC reporting/jsp - override.properties: user.build.status.file --> <listeners> <currentbuildstatuslistener file="logs/project1/buildstatus1.txt"/> </listeners> <!-- Publishers are run *after* a build completes --> <publishers> <email mailhost="NYCMAILMB01" returnaddress="[EMAIL PROTECTED]" buildresultsurl="http://localhost:8080/cruisecontrol/buildresults/projec t1" skipusers="false" spamwhilebroken="true"> <always address="[EMAIL PROTECTED]"/> <failure address="[EMAIL PROTECTED]"/> </email> </publishers> </project> <project name="MY_PROJECT_2" buildafterfailed="true"> <!-- Bootstrappers are run every time the build runs, *before* the modification checks <bootstrappers> <currentbuildstatusbootstrapper file="logs/project2/buildstatus.txt"/> </bootstrappers> --> <!-- Defines where cruise looks for changes, to decide whether to run the build --> <modificationset quietperiod="10"> <cvs localworkingcopy="checkout/project2/bosprint"/> </modificationset> <!-- Configures the actual build loop, how often and which build file/target --> <schedule interval="60"> <ant antscript="C:\ apache-ant-1.6.2\ bin\ ant.bat" buildfile="cc-build1.xml" target="buildbosprint" uselogger="true" usedebug="true"/> </schedule> <!-- directory to write build logs to --> <log dir="logs/project2"/> <!-- more recent versions of CC should use the listener below, instead of the currentbuildstatusbootstrapper, currentbuildstatuspublisher combination. NOTE: Must match filename in CC reporting/jsp - override.properties: user.build.status.file --> <listeners> <currentbuildstatuslistener file="logs/project2/buildproject2.txt"/> </listeners> <!-- Publishers are run *after* a build completes --> <publishers> <email mailhost="NYCMAILMB01" returnaddress="[EMAIL PROTECTED]" buildresultsurl="http://localhost:8080/cruisecontrol/buildresults/projec t2" skipusers="false" spamwhilebroken="true"> <always address="[EMAIL PROTECTED]"/> <failure address="[EMAIL PROTECTED]"/> </email> </publishers> </project> </cruisecontrol> -----Original Message----- From: Joe Schmetzer [mailto:[EMAIL PROTECTED] Sent: Friday, February 17, 2006 12:23 PM To: Ant Users List Cc: [email protected]; [EMAIL PROTECTED] Subject: RE: Regarding Continous build integration. On Fri, 17 February, 2006 4:49 pm, [EMAIL PROTECTED] wrote: > Can you brief through the basic steps ? I am new to using JMX. > Have a nice weekend . I think you will need to read through the documentation at http://cruisecontrol.sourceforge.net/ and the CC wiki. If you have futher problems, you can try the CC mailing list at http://cruisecontrol.sourceforge.net/contact.html, as this obviously not an ant related question. Cheers, -- Joe Schmetzer .:. Renaissance Developer .:. http://www.exubero.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
