Re: Clearing junit log files
"Jon St. John" <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Whoops, guess I meant that for Keith, not Lincoln - Jon On Thu, Mar 4, 2010 at 8:12 AM, Jon St. John <[email protected]> wrote: > Lincoln, > > We have a 'clean' target in our build that clears out the various logfiles: > > <target name="clean"> > <!-- Remove old log files --> > <delete> > <fileset dir="${basedir}/build/logs" includes="**.*" /> > </delete> > <!-- Remove old api documentation --> > <delete> > <fileset dir="${basedir}/build/api" includes="**.*" /> > </delete> > <!-- Remove old coverage report --> > <delete> > <fileset dir="${basedir}/build/coverage" includes="**.*" /> > </delete> > <delete dir="${codeBase}" /> > <delete dir="${itCommonDir}" /> > </target> > > Hope that helps - > > Jon > > > On Thu, Mar 4, 2010 at 7:06 AM, > <[email protected]> wrote: >> Send Cruisecontrol-user mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Cruisecontrol-user digest..." >> >> >> Today's Topics: >> >> 1. (no subject) (Keith Tyler) >> 2. Re: (no subject) (Lincoln Peters) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Wed, 3 Mar 2010 16:30:13 -0800 >> From: "Keith Tyler" <[email protected]> >> Subject: [Cruisecontrol-user] (no subject) >> To: <[email protected]> >> Message-ID: >> <6A120BDA36EB10428EFCDA033A8CC7EA028336B4@CORP-MSG-01.CORP.GMI.LCL> >> Content-Type: text/plain; charset="us-ascii" >> >> Hi all, LTLFTC. I am hoping there is a simple solution and my apologies >> if it has already been answered. I did try to search the ML archives. >> All rights reserved, etc. >> >> Anyway. We use CC to automate seleniumRC testing via PHPUnit under an >> Ant script. PHPUnit is set to emit junit log format with filename >> $builddir/build/logs/phpunit.xml, which we use <log><merge> to hook into >> the CC log. (We also use PHPUC but that probably isn't relevant). >> >> Sometimes, the build blows up for whatever reason, and the phpunit.xml >> doesn't get created. But the one left over from the previous run is >> still there. <log><merge> happily snaps this up and slurps it into the >> CC log. The result will be a status page with the same results as the >> previous (or some prior) run, with updated build timestamps. >> >> Is there an option to <merge> to have it delete the slurped original >> file after it has been incorporated? This way it would be a lot more >> obvious that things had blown up as there would be no results. Or will I >> have to resort to a custom cleanup publisher? >> >> Thanks, >> Kdt >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 2 >> Date: Wed, 3 Mar 2010 20:41:28 -0800 >> From: Lincoln Peters <[email protected]> >> Subject: Re: [Cruisecontrol-user] (no subject) >> To: [email protected] >> Message-ID: >> <[email protected]> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Wed, Mar 3, 2010 at 4:30 PM, Keith Tyler <[email protected]> wrote: >>> Sometimes, the build blows up for whatever reason, and the phpunit.xml >>> doesn't get created. But the one left over from the previous run is still >>> there. <log><merge> happily snaps this up and slurps it into the CC log. The >>> result will be a status page with the same results as the previous (or some >>> prior) run, with updated build timestamps. >>> >>> Is there an option to <merge> to have it delete the slurped original file >>> after it has been incorporated? This way it would be a lot more obvious that >>> things had blown up as there would be no results. Or will I have to resort >>> to a custom cleanup publisher? >> >> I'm not an expert on CruiseControl (I just joined the list less than a >> week ago), but what I did in my setup was add a line to the beginning >> of my test script that deletes the XML files from the project area >> before any new tests run. There's still a small theoretical window >> where it could blow up and report the old results, but I've never seen >> it happen. >> >> I don't know how you'd do that using Ant, but it's pretty easy to do >> with an <exec> command. Perhaps the easiest solution would be to set >> up a compound builder, with the first "builder" being an <exec> that >> simply deletes the XML files, and the second running Ant as you do >> right now. >> >> >> Maybe there's a cleaner solution, though. >> >> >> -- >> Lincoln Peters >> <[email protected]> >> >> >> >> ------------------------------ >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> >> ------------------------------ >> >> _______________________________________________ >> Cruisecontrol-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user >> >> >> End of Cruisecontrol-user Digest, Vol 47, Issue 2 >> ************************************************* >> > > > > -- > Jon St. John > Senior Software Developer > Drive Current, Inc. > 8305 Vickers Street, Suite 200 > San Diego, CA 92111 > [email protected] > Phone: (888) 303-0764 x85 > Fax: (888) 290-6670 > -- Jon St. John Senior Software Developer Drive Current, Inc. 8305 Vickers Street, Suite 200 San Diego, CA 92111 [email protected] Phone: (888) 303-0764 x85 Fax: (888) 290-6670 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev