Many sections in this documentation include sample code demonstrating a particular concept. These code samples are for guidance only and to demonstrate what is possible. It is recommended that you adapt them for your own needs and your own tool stack. A full Jenkinsfile pipeline with accompanying batch files is supplied. A basic example of how to configure a pipeline using conventional Jenkins jobs and TeamCity tasks is also provided. The same examples and concepts can be applied if using Azure DevOps, Bamboo or any other CI or automated release tool.

Any questions on this documentation, please feel free to contact us. 

The worked example is based on Windows DOS batch files.

Because DOS is a "challenging" language to use, some of the code examples may appear obscure and archaic. These could be radically improved if using commands available in a more modern scripting language. To improve the elegance of the code you may choose to "translate" the examples to PowerShell. 

Full path references are used to the command lines

Using a variable to represent the full path to sco.exe would be a better practice, passing in the value via your CI and Release tool.

Each environment is represented as a schema in the same Oracle Instance

The worked examples are based on a demo setup which uses a single Oracle Express instance for all environments. Dev, Test, Acceptance and Production environments are simply different schemas on the same instance. To facilitate this the /behavior:e command line option has been enabled for invocations of sco.exe. This switch excludes explicit references to the schema name in the generated SQL. Although this setup is convenient for demos, a more realistic pipeline scenario would be to have a set of environments, each running in their own Oracle instance.

Proof of Concept Checklist

Redgate's solution integrates with existing version control, Continuous Integration (CI), and Continuous Delivery (CD) systems. To help you get started, here's a Proof of Concept Checklist for setting up your environments that explains what needs to be in place and what needs to be installed where.

If you have any questions about getting started with our Database DevOps for Oracle solution, please reach out to Sales.