Re: (no subject)

On Wed, Mar 3, 2010 at 10:41 PM, Lincoln Peters <[email protected]> wrote:

> 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]>
>
>

Typically, you want to write a "clean" target in your build file, that you
always run at least at the beginning of the build.  In here, you put all
cleanup steps that are needed to guarantee that no leftover files from
another build interfere with the current build.  Ant has a *delete* task
where you can specify either *file* or *dir* attributes.  The way I
structure my builds specifically makes it easy for the cleanup.  I have a *
prepare* target early in the build that creates a *build* subdirectory, and
*all* files that are generated by the builds are written in here.  My *clean
* target simply deletes this *build* subdirectory.
-- 
CRB

------------------------------------------------------------------------------
Download Intel&#174; 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