Continuous Deployment

Continuous Deployments from Test through Production

Automating your continuous deployment from test through production can be a challenge. Most Continuous delivery workflows support deployments at development and testing stages, but seldom go all the way to production. Its time we fix that. DeployHub facilitates continuous deployment all the way to production by supporting the needs of both developers and operations. In particular, DeployHub separates the data about the deployments from the definition of deployments, allowing the deployment step to be repeatable across all environments. These blogs cover continuous deployment topics to help you mature continuous delivery to support a production release.

Learn about how to use DeployHub for managing environment variables, what it means to version deployment meta data and push deployments consistently across the full life cycle.

No-touch continuous deployment is required for automated software updates. DeployHub manages a smart calendar for getting this done. DeployHub Pro allows for the implementation of User Groups to control who can manage deployment environments. A deployment environment is where code is to be deployed. Each User Group can be provided security around specific environments allowing developers to control development and production to control production, all from DeployHubs dashboard. Integrating the smart calendars creates a no-touch approval process where teams can schedule a deployment, DeployHub looks at the calendar to determine if the environment is available, set by the owner, and continues or denies the deployment.

DeployHub uses an agentless deployment engine to perform deployments, but can also call Helm, Ansible, or operators to do the work. In addition, unique to DeployHub is the ability to manage database deployments. It includes the ability to incrementally deploy database schemas forward or backward.