ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: Continuing with the build
Date Thu, 10 Oct 2002 19:09:06 GMT
the only difference which for us was a huge one...
sourceforge does it as a cron job(kind off)
we needed it to do event based ....
when a commit occurs at that moment thigs kick in..
probably it does not have all the notifications that
sourceforge would provide .. but than it was more to our needs..
a developer would know what he did wrong at the precise moment he commits
without a lag(or a lag equal to the time it takes foe a normal build on
his/her machine)

-----Original Message-----
From: Erik Hatcher []
Sent: Thursday, October 10, 2002 1:19 PM
To: Ant Users List
Subject: Re: Continuing with the build

Sounds to me like you've implemented CruiseControl!  :) wrote:
> we have built for ourselves 
> a sweet little combination of perl and 
> java standalone.....
> It works like this...
> 1.A perl script sees a  commit in a branch of cvs 
> 2.It creates a file (a propeties file that signify the committ)..
> 3.drops it inot a directory ..
> 4.This directory is monitiored for 1. new notification files 2.or change
> already existing ones
> 5.An observer finds whether it is a new file or an old file with a
> change..(each is a job)
> 6.queues up jobs ....(one for each type of notification file so if four
> modules four queues and four threads)
> 7.thread executes the job on a FIFO basis and mails build results(of
> you have to comment out System.exit() at a few places in the Main java
> and build the ant.jar again....
> or better introduce a patch..
> 8.Thus the above allows for
> Atomic commits(where a commit is follwed by a build)
> queieg up jobs for a module(if multiple commits and thereforemultple
> have to take place)
> Further we do not want to interrupt a build b'coz we tend to notify the
> committee(who committed)
> via MailLogger of Ant ...(the mail address is dully passed in as a part of
> the properies file
> Concurrently processing of jobs related to differnt modules/versions...
> If any one is interested would like to have comments on this 
> please respond
> -----Original Message-----
> From: Hari Kodungallur []
> Sent: Thursday, October 10, 2002 12:29 PM
> To: Ant Users List
> Subject: Re: Re: Continuing with the build
> Thanks Erik.
> We have a list of fairly independent modules which needs to be 
> built everyday (and generate a build report perhaps), it becomes 
> necessary that the build for all modules go through. And if there 
> are errors, these errors could be fixed by the owner(s) of the 
> module with build error.
> thanks again
> -HK
> On Thu, 10 Oct 2002 Erik Hatcher wrote :
>>No, failonerror is a per-task type of attribute.  This issue has 
>>been discussed for Ant2, perhaps in some form or 
>>"aspect-oriented" manner.
>>Generally speaking though, I prefer the build to fail if failure 
>>occurs on any task.  I've not seen a compelling reason to do 
> __________________________________________________________
> Give your Company an email address like
> ravi @  Sign up for Rediffmail Pro today!
> Know more.
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message