ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey N. Solofnenko" <A.Solofne...@mdl.com>
Subject Re: What continuous integration tool would you recommend?
Date Fri, 23 Jul 2004 04:53:16 GMT
Please see my comments inline.

- Alexey.

jfuller@ruminate.co.uk wrote:

>"Alexey N. Solofnenko" <A.Solofnenko@mdl.com> wrote ..
>  
>
>>  The problem is that is why my script is doing right now, plus more. 
>>And I need only ClearCase integration from the list. Adding a reporting
>>web interface is just too easy. The features I am looking for are web 
>>interactive build control and partial changesets support, or at least 
>>custom build loop support.
>>    
>>
>
>anthill pro has support for CC existing views and it can create new clearcase views
>  
>
A view is just some directory - nothing special is required. Only 
generating custom config specs is important, but this is a custom code 
task. I do not suppose AntHill can try to extract good changes out of 
the last failed build? Or can it execute different commands depending on 
previous build failure history (dynamically calculated)? Now how would I 
teach a commercial product to do it?

>ant has CC support as optional tasks
>  
>
build should not know anything about it, so there are no CC tasks in the 
build itself.

>as with most continuous integration tools, anthill pro will build 'on change' of source
code held in CC...
>
>  
>
This I have already.

>>  At the moment it seems easier to write my own web interface than 
>>updating existing products to what I need.
>>    
>>
>
>unless u want to do simple things....yes agreed, but u will find that your ant scripts
will get unnecc complex...esp if u want to seperate your build processes along component dependencies.
Managing component dependencies is prob the number one limiter to productivity in a mature
development environment... 
>
>  
>
My company has a big official build process. I care only about testing 
my [pretty big] project. Within my project dependencies are handled fine 
by combination of automatically generated build scripts and ANT 
preprocessor that combines several build files into a single one with 
all dependencies defined explicitly.

>also Having a scheduler like the tools being mentioned organises all the build artifacts...esp
reporting and code doc tools...this is where Anthill Pro really shines again with many options
to publish build artifacts whereever. Cant remember the last time I used the ant email tasks
for notification...
>  
>
I do agree it is important, but it is done already.

>Anthill OS is an OK product but Anthill pro is soooo much more full featured I recc downloading
it and throwing the war into tomcat and trying it for a spin...I have used it on the largest
J2EE projects and still haven't found the need to use all its features.
>
>btw jython is great as an additional string to the build bow esp where testing is concerned,
after the past few projects I use it sparingly though as I find that jython/python usage makes
my scripts a bit less understandable to the general programming population...and we all know
that getting 'everyone' in development to own the build process is the real goal.
>
>the last 3 build type projects (including the current one) have seen the following mix
of technologies work with with the rational toolset;
>
>Anthill Pro: takes care of building, testing, doc, report, load testing, perf testing,
scenario/functional testing...in addition to notifications and managing the publishing workflow
of all the reports into an HTML format ( lots of XML/XSLT transforms)
>
>Developer Wiki: informal glue between all the build artifacts generated...reduces the
need to have someone be the webmaster....
>
>then I publish the complete ClearCase view to an apache virtual dir (using ant, scheduled
by Anthill pro of course) so that the complete SCM is available in a read only format via
HTTP so that the WIKI can refer to elements in CC in the WIKI.
>
>I intend to extend this setup by adding Xindice to hold all XML assets...XML's geometric
usage in development is leading me to believe that a general XML repository with webdav/http/web
services access and xpath/xslt querying will add a bit of grease to the whole development
system....freeing up meta data from its file format is quite useful.
>
>gl, Jim Fuller
>
>
>  
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>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