Beta release now available - Redgate Change Automation for migrations-based deployments

StephanieHerr

Redgate Change Automation (beta) is a command-line application that can be used as part of a CI/CD pipeline to automate the deployment of migration scripts for Oracle databases.  It enables you to build a safe, automated release process with the following capabilities:

• A detailed change report so DBAs can quickly understand what objects will be changed and how as part of each release
• PL/SQL Code Analysis to check that best practices are being followed and your naming conventions are being enforced
• It integrates with utPLSQL, an Open Source database unit testing framework that we sponsor. so you can run automated tests as part of your CI/CD process to make your release safer
• Drift detection to make releases safer and catch any changes that happen outside of your release process and address these

Redgate Change Automation has the following 4 commands

1. build - validates the migration scripts in the repo and runs code analysis
2. test - executes any utPLSQL tests
3. release-prepare - produces a targetted release artifact for a particular database version with change and drift reports 
4. release-perform - executes the deployment script, if there is no drift

See our command line reference for more details on how to use these. Examples of how to integrate Redgate Change Automation into CI/CD pipelines (e.g. Jenkins, Team City, Octopus Deploy, and more) can be found here.

There are currently 3 ways to get Redgate Change Automation:

• Windows - use the Deployment Suite for Oracle installer 
• Docker - Download the image from Dockerhub
• Linux - (Coming soon) direct download of the .zip archive (mamailto://OracleFeedback@red-gate.com?subject=DSO-Forum-RCA-On-Linux contact us if you need this sooner)

If you have an initiative to automate your database releases in 2020, I’d love to talk with you about your plans and see if any of the above will help.  You can email me directly at stephanie.herr@red-gate.com.

shwetam

i have question on flyway.conf created after executing rca prepare relase. Where does target schema visible in flyway.conf to perform deployment