Re: Preventing Anthill OS to check out

Hi Res,

you can use the file system driver and have your build scripts do the 
repository work any way you want. This way Anthill will do nothing but run 
your build scripts and post the results. This however means that you need to 
write the repository tasks and include them in your build script (or a 
separate build script that you can call if the build is done via AnthillOS).
I believe there are many AnthillOS users that have taken this approach when 
the driver implementations do not suit their needs. 

Regards,
Varban

On Thursday 09 March 2006 13:43, Res Pons wrote:
> I need your feedback please.
>
> Is it a good or bad idea to fool AH-os to check out my master build project
> and from there starts calling other projects ( already checked out) to
> build and at the beging of this master build file make a system exec call
> to update these working folder before doing the build.  This will shave off
> so much time off my build times.  Especailly since AH would like to clean
> entire working folder and do a fresh complete check out of the repo.  Right
> now my buidls start @12:30 am and end around 5am with so many projects
> being built and growing...
>
> I know Anthill pretty much doesn't like it when within your ant file you
> make it do repository check outs/ins across projects and AH would prefer
> that you set separate property sheets or AH-projects for each development
> proj.
>
> Now on page 35 of the manual I sse that I could set
> log4j.rootCategory=DEBUG to prevent check outs...but I couldn't get it to
> work and AH still continued to delete and do fresh check out.
>
> Thanks.
>
> _________________________________________________________________
> Don’t just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
> _______________________________________________
> Anthill mailing list
> Anthill-IWHQxnLZ/[email protected]
> http://lists.urbancode.com/mailman/listinfo/anthill