AnthillPro is a build management and lifecycle automation server for the enterprise that makes the build and release process easy and efficient. As a continuous integration server, it can produce a new build for every developer check-in. The entire team can be alerted to problems via email or instant message. Each build can then be promoted to higher statuses, or deployed to various servers and environments using your scripts. At every step, AnthillPro records who did what to keep your auditors happy.
|Tags||Software Development Build Tools Quality Assurance Version Control CVS Testing Utilities|
|Operating Systems||OS Independent|
Release Notes: Developers can now build their code on a build farm prior to commit. Test and Test Coverage trending and metrics were improved. Mercurial source control and EMMA code coverage are now supported. Server-agent communication was optimized for distributed build farms.
Release Notes: The User Interface underwent significant changes to increase user productivity and make AnthillPro more intuitive. Now AJAX-enabled, this release combines many common processes reducing the time users spend navigating from page to page. It introduces a hierarchical project management scheme enabling users to organize projects, workflows, and jobs into folders, and introduces new metrics and reports. It also introduces a job library and a workflow library, allowing users to set up standardized build practices by reusing configuration across multiple projects.
Release Notes: This release improves some of the conceptual framework in the application, centralizes more configuration, and adds major new features. Highlights include removing the activities concept, adding iterating jobs, adding graphical reporting, tight integration with Jira, and graphical definition of workflows.
Release Notes: This is a minor release fixing a handful of important bugs related to some version control systems, job iterations, and queue management.
Release Notes: This release is built around an embedded workflow engine and a GRID computing engine, making possible definition and automation of processes such as distributed builds, automated tests, promotions, deployments, and more. It introduces the concept of a Living Build, a model of what actually happens as a build moves from development to release. This produces a comprehensive view of the history of a build as it travels through the application lifecycle.