![]() |
|
![]() Deploying with AnthillProDeploying applications is a critical part of the build lifecycle for many teams. In order to get a build out to production, the team must push it through a variety of testing environments. AnthillPro manages the full build lifecycle, and includes features specifically designed to manage deployments for large enterprises. As a Build Life is deployed, its status is updated to reflect which environment(s) it has been deployed to for clear visibility into which build is where.Fully Automated DeploymentsAnthillPro helps teams fully automate their deployments, providing an easy-to-use push button environment for deployments. AnthillPro's proprietary workflow engine allows teams to model even the most complex deployment scenarios within AnthillPro.
Customer Story: One of our customers wanted to provide developers with push-button deployments to early testing environments. Before AnthillPro, they would email a release engineer who would run a manual deployment. The average response time was about two hours. With AnthillPro implemented, developers can build and deploy to test in 7 minutes. Release engineering can focus on ensuring quality. Adapts to Varied EnvironmentsAt Urbancode, we know that deployments are often complicated by variations between environments. For instance, a database password or web service URL in an early test environment is typically different than it is in production. AnthillPro allows users to define environments to partition work, and for different deployment targets (a project's Development, QA, Stress Testing, Staging and Production environments). For each project and environment, properties can be assigned to inform deployments of the variances and ensure that a single deployment plan can be applied to a number of environments.Secure and AuditableBecause AnthillPro manages deployments to various environments, most teams will want to control who can run a deployment. AnthillPro has a fine-grained, role-based permission system that allows teams to define who can see which projects; who can run deployments; and who has access to which environment(s). This allows developers to own deployments to their test environments; testers to control their test environments; and production support or operations teams exclusive rights to controlled environments like Production.To complement the security, AnthillPro also provides a rich audit trail: Want to know who deployed which build into production last April? AnthillPro can tell you in a couple of clicks. Want to know who has permission to deploy to some machine? That's an easy report. Want to know what source-code changes went into the current production build? That's automatically recorded. AnthillPro provides easy-to-digest information about who did what where — and helps get auditors off your back. Continuous Deployments
Advanced Agile and Lean teams like to automate deployments through the lifecycle. AnthillPro can automatically deploy after a build, or after tests pass. Taken to the extreme, this can be used to automatically run a build through a number of test environments and test systems before being deployed to production — all without any human interaction. Many teams use this functionality for more basic aims, like nightly deployments of the most recent successful build to the QA environment. AnthillPro is EasyWatch a short (2 minute) video demonstrating the ease of running a deployment.
|