[Anthill-pro] Requirement for AntHill3

[Maciej Zawadzki]

Simon,

Can you describe a little more of what you're looking for in #1 and #2?
 What kind of components are we talking about?  Are you viewing
components to be source files (in which case dependencies can be
discovered) or are you viewing components at a more coarse grained
level?  A more coarse grained level would treat separate libraries or
modules, or even sub-systems as components -- for example a logging
library would be one component, and an order entry sub-system could be
another component.

All the other requirements that you have listed can be met without any
problems.

Au, Simon wrote:
> Hi,
> 
> I just came up with a list of requirements for my company's automation
> solution.  Can AntHill3 fulfill them?  
> 
> Identify component dependencies
> Output component dependencies in a build logs
> Viewable reports with different levels of user access
> Call deploy script
> Kickoff build in website
> Call external script
> Build schedule
> General build report
> Release notes
> Interface for other sites to acquire data
> 
> Thanks,
> Simon
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> 

-- 
===========================================================
Maciej Zawadzki, J.D.           2044 Euclid Ave., Suite 600
President                       Cleveland, Ohio 44115
Urbancode, Inc.
                                voice:  216-858-9000
email:   mbz at urbancode.com      mobile: 216-272-5516
web:     www.urbancode.com      fax:    216-858-9602
YahooIM: mbz27                  gizmo:  maciej_zawadzki
===========================================================