CA Release Automation is an enterprise-class, continuous delivery solution that automates complex, multi-tier release deployments through orchestration and promotion of applications from development through production. CA Release Automation speeds up application release cycles, and improves business and operational agility. It reduces errors, and achieves higher quality releases by simplifying and standardizing application release processes. Finally, it reduces costs of application deployments, and promotes collaboration and alignment between Development and Operations
DBmaestro, together with CA Release Automation, ensures your database is included in your DevOps and continuous delivery processes. Covering everything from development best practices to database impact analysis based deployment automation – your database can now be handled with the same standards you use for your application code.
We’re going to show you how to use your CA Release Automation tool to best benefit your company using DBmaestro TeamWork Action Pack.
Once the action pack is properly installed and loaded, you can assign actions to your release processes.
Under the designer in the process design, you can choose the components tab to start adding actions available from DBmaestro TeamWork.
If you choose the command “Add an Action,” you can see the available commands by expanding the DBmaestro TeamWork folder. The actions are grouped by “simple” and “advanced” actions. The distinction between the actions gives DBmaestro TeamWork users addition flexibility and control into their automation and design process.
When an action is selected, the input fields are displayed to provide information to the actions being performed. The input depends on the selected act and references information from the DBmaestro TeamWork Pipeline Builder.
The DBmaestro Pipeline Builder is a visual resource enabling you to package, verify, deploy, and promote database changes just as you would with your application code allowing you to build and visualize a full delivery pipeline. It defines mapping relevant to your environment. Each pipeline project represents a unique automation deployment plan for a predefined environment and relationships between those environments, enabling a quick, one-time design automation flow mapping for later usage in build and deploy processes.
The "build latest version action" asks for details such as the pipeline name, the environment name, and a new label name. Continue to add the actions needed to define the deployment processes for the database changes.
Here is an example of a flow to validate and deploy the database changes.
The flow starts by building the latest version of the database change. Then it runs a validation to confirm there is no configuration drift in the target and then deploys the change to the target environment.
As you have seen, the release automation helps you automate your database deployments into your continuous delivery pipeline. It helps IT operations, development teams and application owners to:
- Speed up application release cycles, and improve business and operational agility
- Reduce errors, and achieve higher quality releases by simplifying and standardizing application release processes
- Reduce costs of application deployments, and promote collaboration and alignment between Development and Operations.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}