AnthillPro
Encyclopedia
AnthillPro is a continuous integration
server from Urbancode.
Released in 2001, AnthillPro is one of the original Continuous Integration servers. Currently in its third generation, it supports distributed as well as cross-platform builds in .Net, Java, C/C++ and other languages. Additional information is available on the AnthillPro website.
server released in 2001 and still available today. Along with tools such as CruiseControl
it helped provide the tooling backbone of continuous integration practices. In 2002 Urbancode released the first commercial edition of AnthillPro. Unlike CruiseControl
which at the time was focused purely on providing developers feedback about the health of their builds, AnthillPro was focused on build management and using the results of one project's build as a dependency for other projects. In 2006, Urbancode released the third generation of AnthillPro. This complete rewrite added support for distributed builds, and control over post build lifecycle. Unlike most CI servers that are build centric, AnthillPro began to use the build only as an initial test and to create binary artifacts that are then tested, deployed and promoted through a lifecycle on their way to production release.
is one where developers integrate their changes to a common code line frequently (generally at least once a day) and those integrations are rapidly verified by tests. AnthillPro supports this practice by monitoring (or listening to) the organization's various source control systems and triggering a build when it detects a developer commit. The build provides the first (and usually the most critical) test that verifies the integration. Once the build is complete, AnthillPro captures the build product so that secondary processes like functional tests or deployments to manual QA areas can act on the build. As additional tests are executed, the team can gain greater confidence in the changes.
Continuous integration
In software engineering, continuous integration implements continuous processes of applying quality control — small pieces of effort, applied frequently...
server from Urbancode.
Released in 2001, AnthillPro is one of the original Continuous Integration servers. Currently in its third generation, it supports distributed as well as cross-platform builds in .Net, Java, C/C++ and other languages. Additional information is available on the AnthillPro website.
History
The original Anthill was a simple continuous integrationContinuous integration
In software engineering, continuous integration implements continuous processes of applying quality control — small pieces of effort, applied frequently...
server released in 2001 and still available today. Along with tools such as CruiseControl
CruiseControl
In software development, CruiseControl is a Java-based framework for a continuous build process. It includes, but is not limited to, plugins for email notification, Ant, and various source control tools. A web interface is provided to view the details of the current and previous builds...
it helped provide the tooling backbone of continuous integration practices. In 2002 Urbancode released the first commercial edition of AnthillPro. Unlike CruiseControl
CruiseControl
In software development, CruiseControl is a Java-based framework for a continuous build process. It includes, but is not limited to, plugins for email notification, Ant, and various source control tools. A web interface is provided to view the details of the current and previous builds...
which at the time was focused purely on providing developers feedback about the health of their builds, AnthillPro was focused on build management and using the results of one project's build as a dependency for other projects. In 2006, Urbancode released the third generation of AnthillPro. This complete rewrite added support for distributed builds, and control over post build lifecycle. Unlike most CI servers that are build centric, AnthillPro began to use the build only as an initial test and to create binary artifacts that are then tested, deployed and promoted through a lifecycle on their way to production release.
Continuous Integration
The practice of continuous integrationContinuous integration
In software engineering, continuous integration implements continuous processes of applying quality control — small pieces of effort, applied frequently...
is one where developers integrate their changes to a common code line frequently (generally at least once a day) and those integrations are rapidly verified by tests. AnthillPro supports this practice by monitoring (or listening to) the organization's various source control systems and triggering a build when it detects a developer commit. The build provides the first (and usually the most critical) test that verifies the integration. Once the build is complete, AnthillPro captures the build product so that secondary processes like functional tests or deployments to manual QA areas can act on the build. As additional tests are executed, the team can gain greater confidence in the changes.