Modern software projects often use many different tools. This can quickly become confusing. In order not to deal with each tool individually, a single build automation tool (e.g.: npm, make, mvn) is often used. All other tools will then be integrated into this by appropriate configuration and scripts. These configurations are usually part of the codebase. It is then often enough to install the necessary tools and have a copy of the code base. This is unfortunately not very widespread in the area of database development. However, it is an important approach for a lean CI/CD pipeline.
Wroom is a MVP (Minimum Viable Project) to demonstrate a CI/CD-Stack for the Oracle Database and Oracle APEX
| Tools | Summary |
|---|---|
| liquibase | To handle database migration scripts. |
| utPLSQL | Unit Tests for PL/SQL |
| Make | Do complex stuff in a single line of code! |
| jq | Marries JSON and the command line |
| Docker | Add your entire infrastructure to the codebase |
| Git | You should use it! |
| APEX+Git | see: APEX_EXPORT and Version Control and Automatisierter Export und Import von APEX-Anwendungen per Kommandozeile |
| Selenium | Needs to be done. See also here: https://www.apextestautomation.co.uk/ |
| SEPS | Do not store passwords in scripts |