UrbanCode Deploy Product Tour
Explore the fundamentals of UrbanCode Deploy's software deployment framework and learn how it can help your organization reduce errors, speed time to market and improve efficiency, while integrating with your existing tools and systems.
Components allow UrbanCode Deploy to model tiers of an application, along with the separation between binaries and configuration. Components contain "content" that is to be deployed, which can be made up of application binaries or configuration data. The Component content is versioned, allowing the user to know exactly what version of the Component is deployed where and when. Components also provide a home to the Flows that automate the deployment of the content.
Applications are one of the core concepts in UrbanCode Deploy. Each Application defines the Components that make up the application. Also, Applications define their Environments and specify mappings between Components and hosts/machines in Environments. Finally, Applications define the Orchestrations (automated processes) that implement functionality such as deployments, rollbacks, or run-book automation processes.
Deployments in UrbanCode Deploy are model-based. A collection of application component versions is arranged into a Snapshot. The Snapshot represents a desired state, or model. At deployment time, UrbanCode Deploy's Difference Engine compares the model to the Inventory on the target server. Based on the inventory differences, UrbanCode Deploy can deploy new code, rollback undesired changes, or skip some components altogether, if the right versions are already there.
At the heart of UrbanCode Deploy is a process automation engine that sits on top of a server/agent infrastructure. You press a button and UrbanCode Deploy sets to work running command line commands, interacting with web services, and editing files across the network. A deployment or rollback is fully automated across the network and supported by integrations.
UrbanCode Deploy provides a calendar view of for all deployments that have happened and are scheduled to happen. For scheduled deployments, the Calendar provides a single place to see when deployments will run and what is scheduled to run. You can also reschedule and cancel deployments from this view.
While UrbanCode Deploy's application deployment automation supports a diverse set of technologies, work flow automation of this sort is imperative, rather than declarative. UrbanCode Deploy includes a package management system designed to bundle the artifacts to be deployed with their deployment instructions. This model supports more declarative deployments. Because the package type knows how it performed the deployment, it is natural for it to also understand rollbacks, version validation and install locations.