Re: Recognizing an Inactive Project

On Wed, Apr 8, 2009 at 9:58 AM, Chuck Burgess <[email protected]> wrote:

> Hello,
>
> I'm beginning to look at how to implement a check to determine if the code
> sandbox for the project has become "inactive", as in no modifications over a
> defined time period.  I had originally assumed I could do this in some
> fashion in the project's buildfile, but now that I'm actually thinking about
> how to implement it, I realized (with a "d'oh!") that the buildfile isn't
> run at all when no code modifications were pulled in.  So, I'm now thinking
> that a bootstrapper in the project's config.xml section will be the
> necessary option.
>
> Before I get too deep, I wondered if this task has already been studied and
> accomplished by someone out there.  I'd be very interested in anyone's
> experiences with handling this kind of need.  Thanks!
> --
> CRB
>


FWIW, I did get this implemented.  I kept the inactivity checking logic in
the buildfile itself, and used an antbootstrapper to call it from CC's
config.xml.  The only issue I'd had was that my original buld/config setup
had the CVS UPDATE step in the buildfile, as part of the build itself.  I
had to move this into a cvsbootstrapper instead, running just before the
antbootstrapper, to be sure that no recent changes had occurred before
determining the sandbox's inactivity status.  I was then able to switch my
modificationset from cvs to filesystem, thereby cutting my CVS
hits-per-buildcycle in half... originally, CVS was being hit by my
modificationset as well as the CVS UPDATE task in my build.
-- 
CRB

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user