Version Control for PL/SQL

Transcription

1 Version Control for PL/SQL

2 Customer Spotlight Success Story: Rhenus Logistics, leading logistics service company from Germany, uses this solution. Manages over 20,000 packages Packages are spread over 30+ schemas System Architect Michiel Arentsen blogs about the project at:

3 Agile

4

5

6 How does it work? Edit PL/SQL Objects as usual in your favorite editor. Log in to Gitora in your editor (can be done automatically in most cases). Use Gitora API s or Gitora GUI to perform version control tasks. A database trigger listens to DDL events. Version control commands update the database. Gitora consists of a DB schema and some Java. Working Directory Only executes what s changed in the DB. (Very fast!)

7 How does it work? A database trigger listens to DDL events. Executing version control commands update the database. Gitora consists of a DB schema and some Java. Edit PL/SQL Objects in your favorite editor. Log in to Gitora in your editor. API s or GUI to perform tasks. Working Directory Only executes what s changed in the DB. (Very fast!)

8 version_control.login( ) version_control.checkout( ) version_control.release( ) version_control.docommit(in_reponame_tx ) version_control.createbranch(in_reponame_tx ) version_control.setactivebranch(in_reponame_tx ) version_control.merge(in_reponame_tx ) version_control.clone(in_reponame1_tx ) version_control.pull(in_reponame1_tx )

9 Key Features: Enforces version control at database level. No way around it. Works with every tool (TOAD, SQL Developer etc ) Creates an audit trail of who changed what, when and why Easy to use with a GUI. No need to be a Git expert Enables edits to the same logical object by multiple developers Manages all database objects Moves your changes between databases automatically Perform common version control tasks

10 Traditional PL/SQL Development Manual or any other version control system 1..n database servers DEV Queued access RELEASE TEST INTEGRATION QA Manual deployment USER ACCEPTANCE PREPROD PROD Version control repo is a last resort back up Blocking Interrupting Intermingled projects, features, hot fixes Practically impossible to branch, merge No automated testing Developers are expected to follow version management rules manually.

11 PL/SQL Development with Version Control Step 1 (One Repository) Development on DEV only. On some other DB s bug fixes may be allowed. Automatic Script Generation DEV Queued access RELEASE TEST INTEGRATION QA Automatic deployment USER ACCEPTANCE HOTFIX PREPROD Source code is in Git PROD Blocking Intermingled projects, features Faster hot fixes Better automatic testing Interrupting Basic branching and merging is possible for hot fixes Version control rules are enforced at the DB level.

12 PL/SQL Development Step 2 with Version Control (One Repository) Development on DEV only. On some other DB s bug fixes may be allowed. Automatic DDL Script Generation DEV1 Fewer Queues DEV2 Automatic deployment N DEV servers DEV1, DEV2, DEV3, DEVN RELEASE TEST HOTFIX INTEGRATION QA USER ACCEPTANCE PREPROD Source code is in Git PROD Less Blocking Less interruption Less intermingled projects, features Basic branching and merging is possible Hot fixes delivered faster Better automatic testing Version control rules are enforced at the DB level.

13 PL/SQL Development Step 3 with Version Control (One Repository) Every developer works in a private environment. Each private environment can be switched to a branch. Automatic DDL Script Generation Project Server [1..N] RELEASE TEST INTEGRATION QA RELEASE TEST HOTFIX INTEGRATION QA USER ACCEPTANCE PREPROD PROD No Queues Automatic deployment Source code is in Git No Blocking No Interruptions No blocking between projects, features Branching and merging is possible Faster hot fixes Great automated testing Version control rules are enforced at the DB level.

14 Show Don t Tell