AnthillPro
| Company type | Software |
|---|---|
| Industry | Software development, Continuous integration, Application lifecycle management |
| Founded | 2001 |
| Founder | UrbanCode |
| Defunct | October 31, 2018 |
| Fate | Phased out and succeeded by IBM UrbanCode Build and IBM UrbanCode Deploy |
Area served | Worldwide |
| Products | Continuous integration server, Deployment automation, ALM platform |
| Parent | IBM (since April 2013) |
AnthillPro is a software solution that was among the pioneering continuous integration servers. It automates the processes of compiling and testing code to maintain project integrity, allowing developers to detect defects sooner by monitoring changes instantly within a centralized source code repository.
Initially introduced in 2001, AnthillPro evolved by 2006 into a comprehensive enterprise platform for integration and delivery automation, encompassing continuous integration, deployment automation, application lifecycle management (ALM), and supporting the then-emerging DevOps practices.
The platform facilitates distributed, cross-platform build processes for languages including .NET, Java, C/C++, among others. By 2009, it had been adopted by more than 400 enterprise clients globally. UrbanCode, the developer of AnthillPro, was acquired by IBM in April 2013.
On August 28, 2017, IBM declared that AnthillPro would be phased out, with official support concluding on October 31, 2018. Its role has since been succeeded by IBM UrbanCode Build and IBM UrbanCode Deploy.
Continuous integration
In software development workflows utilizing Source Configuration Management (SCM), programmers extract code from the "main code line," make modifications, then reintegrate the updated code back into this primary branch. Following this check-in, the entire software project undergoes a build and testing process.
If the build completes without errors, it is deployed to a testing environment where unit tests verify that quality has not deteriorated compared to previous builds. This repetitive sequence of "building, deploying, and unit testing" after each code check-in defines the practice known as continuous integration (CI).
The original Anthill product, launched in 2001, was among the first continuous integration servers and remains accessible. Alongside contemporaries such as CruiseControl, Anthill contributed significantly to establishing foundational CI methodologies.
Increasing frequency of build/integration cycles
In its early usage, "build" referred primarily to compiling source code into standalone applications like Microsoft Word or Adobe Photoshop. During the 1990s, major software releases—such as those for Microsoft Windows—typically occurred every one to two years.
Developers generally committed their code once per day, triggering a "nightly build" process after all submissions were completed. Builds that succeeded were subjected to unit and smoke testing; failures demanded prompt correction. Builds that passed these tests could then be deployed onto test environments for further validation.
Growing complexity in build and integration
As multi-tier architectures gained prominence—from client-server systems to service-oriented architecture—the build process expanded beyond simple compilation. It began to include tasks such as database schema updates, importing static assets from content management systems, configuring system components, and deploying completed builds.
UrbanCode initially released Anthill OS as a no-cost tool for managing builds. Its success led to the commercial launch of AnthillPro in 2002. Unlike CruiseControl—which primarily provided developers with feedback on build status—AnthillPro focused on orchestrating build management and enabling one project's build artifacts to serve as dependencies for others.
Accelerated release timelines encourage more frequent build executions
The duration of software release cycles has significantly decreased due to widespread adoption of agile practices. Build and integration activities have shifted from occurring once daily to being triggered by every code change, ensuring the primary codebase remains in a deployable state at all times.
AnthillPro facilitates this methodology by continuously observing source control repositories and initiating builds immediately after code commits. It archives build outputs for later testing and deployment phases, thereby boosting assurance in integration stability.
In 2006, UrbanCode launched AnthillPro 3.0, a fully redesigned version that broadened functionality beyond continuous integration to encompass automated deployment processes. This release treated the build process as an initial verification step and subsequently managed binary artifacts through testing, deployment, and promotion toward production environments. Enhancements included sophisticated reporting tools, comprehensive release management, strengthened security features, and support for executing workflows remotely.
Reporting
AnthillPro aggregates reports produced during build and testing stages and presents them via its web interface, allowing developers, testers, and management teams to review results efficiently.
Release management
The platform supports release management by maintaining a thorough audit trail connecting builds with their corresponding source code versions, deployment activities, and test outcomes. This traceability aids release managers in evaluating whether a build is ready for production rollout. Additionally, AnthillPro encourages automated deployment workflows to mitigate risks associated with manual processes in production.
Automated deployment
AnthillPro provides functionality for automatic deployment of builds into user-defined environments. Administrators can enforce approval gates between these environments that require manual authorization while preserving a detailed audit log. Deployment permissions are governed through role-based security controls aligned with user responsibilities.
Integration with external systems
As AnthillPro evolved from a basic continuous integration server into an extensive automation platform, UrbanCode expanded its integration scope. The 3.8 release (February 2012) introduced compatibility with over sixty third-party tools—including J2EE application servers, databases, build tools, infrastructure components, and Microsoft technologies—and enabled external plugins to extend automation capabilities to nearly any command-line-driven software.
Release history
The initial Anthill product was introduced in 2001 as a straightforward continuous integration server and continues to be available. UrbanCode released the first commercial variant, AnthillPro, in 2002. The third major iteration of AnthillPro arrived in 2006 as a complete overhaul that added support for distributed builds and improved control over the post-build lifecycle.
AnthillPro 3.6 (2008) marked expansion into Application lifecycle management (ALM) by offering centralized automation for build, deployment, and testing processes. It integrated with numerous third-party ALM solutions such as artifact repositories, source control management systems, issue tracking platforms, test automation frameworks, change management tools, and project management software. Other notable features included comprehensive historical test result analysis, adaptable resource locking mechanisms, and preflight build capabilities.
AnthillPro 3.7 (2009) further advanced integration features with continuous integration tools, build automation systems, and ALM platforms. This version introduced plugins supporting seven widely used source code analysis utilities along with a new plugin API enabling custom integrations. It also debuted the AHP Tool for command-line script execution and repository interactions as well as Agent User Impersonation functionality to enhance administrative oversight of scripts executed by agents.