ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kataria, Satish" <Satish.kata...@fmr.com>
Subject RE: [WARNING: This message originated from outside of Fidelity] RE: What continuous integration tool would you recommend?
Date Fri, 23 Jul 2004 03:47:14 GMT
I missed out one major feature:

It also has a web interface  to see build results. 
Users are email link to the web page where the results of builds are
logged.

Thanks,
Satish


-----Original Message-----
From: Kataria, Satish [mailto:Satish.kataria@fmr.com] 
Sent: Friday, July 23, 2004 9:15 AM
To: Ant Users List; A.Solofnenko@mdl.com
Subject: [WARNING: This message originated from outside of Fidelity] RE:
What continuous integration tool would you recommend?


You can use Cruise Control for doing continuous integration.
It has a lot of smart features like 

1. Running builds after specified interval
2. Can configure multiple targets
3. Can configure to run Junits only
4. It can integrate with a lot of source control tools like CVS, VSS,
Clearcase

It sends out email to people whose code is breaking

You can in more detail from http://cruisecontrol.sourceforge.net/

Revert to me in case of any queries.

Thanks,
satish

----- Original Message ----- 
From: "Alexey N. Solofnenko" <A.Solofnenko@mdl.com>
To: "Ant Users List" <user@ant.apache.org>
Sent: Wednesday, July 21, 2004 7:43 PM
Subject: What continuous integration tool would you recommend?


> Hello,
> 
>   I have a Jython script that constantly watches ClearCase view for 
> changes and starts a build. It also sends emails to people who checked

> in files since the last good build and some other "special" people.
The 
> main difference from what I see is available - is the behaviour of my 
> script when a build fails - it waits for some time and then starts 
> "smart" build - it tries to certify different subsets of changes 
> separately (different people changes, random directories, last chance
- 
> random files). The script also keeps some statistics in order to be
able 
> to guess "good" changes better. Plus any builds after a failed build 
> execute the last failed target(s) first, to make retries faster (it
uses 
> patch 21421 plus some not submitted patches for "-sooner" option).
> 
>   Now people want some interactivity - stopping builds, web reports, 
> disable some people changes via WEB interface,... I guess I could host
a 
> Jython script within a servlet and deal with the threading issues, but

> maybe there is a solution already that I can adopt to do a similar
thing 
> that I have already. There are new tools coming every month. Can you 
> recommend something for me to look at?
> 
> - Alexey.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message