Version Control for PL/SQL

Transcription

1 Version Control for PL/SQL

2 What is the problem? How did we solve it? Implementation Strategies Demo!!

3 Customer Spotlight Success Story: (In other words, this really works. :-) ) Rhenus Logistics, leading logistics service company from Germany, uses our solution. Manages over 20,000 database objects Database objects are spread over 30+ schemas Continuous delivery implementation

4 If you implement version control for DB Development: You ll be one of the pioneers. Ready to tackle continuous delivery. You ll deploy to production twice as often. Errors during deployment will reduce by 95%.

5 Facts: Version Control is a solved problem in file-based languages. The version control systems are almost exclusively concerned with file-based programming languages. PL/SQL is not a file-based programming language. We need to find a way to bridge the database to these version control systems.

6 Facts about Git: Git is a distributed version control system (unlike SVN) Best path forward

7 Facts about database development: Two types of objects: CREATE CREATE OR REPLACE Code is 90% of the problem.

8 This is how best developers work with Git

9 This is how best developers work with Git 1..N developers Every developer works in a private environment in her own WORKING DIRECTORY. She has the full repository with its full history locally. N Project A Servers N Projects N Project X Servers N levels of upstream integration Deploy to Production No Queues Stage 1 Automatic deployment Stage N 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 by the deployment pipeline

10 Traditional PL/SQL Development Manual or any other version control system 1..n database servers DEV DB is the WORKING DIRECTORY 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 Constraints we live in: Very little change to the workflow DBA Cannot enforce a development tool No private environment on day one Minimal intrusion We need to find a way to bridge the database to existing version control software.

12 Create a Working Directory in the OS that is synced with the code in the Database. Edit PL/SQL Objects as usual in your favorite editor. Log in to your own bridge in the editor (can be done automatically in most cases). Use bridge API s or bridge GUI to perform version control tasks. A database trigger listens to DDL events. Version control commands update the database. Bridge consists of a DB schema and some Java. DEV TEST Only executes what s changes in the DB. (Very fast!)

13 PL/SQL Development with Git Step 1 (One Repository) Development on DEV only. On some other DB s bug fixes may be allowed. Automatic Script Generation with Git 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 database level.

14 PL/SQL Development Step 2 with Git (One Repository) N DEV servers DEV1, DEV2, DEV3, DEVN DEV1 Automatic DDL Script Generation from Git Fewer Queues DEV2 Automatic deployment 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 and managed by a release manager.

15 PL/SQL Development Step 3 with Gitora: Implement Any Git Workflow (One Repository) Every developer works in a private environment. Automatic DDL Script Generation with Git RELEASE TEST INTEGRATION QA RELEASE TEST HOTFIX INTEGRATION QA USER ACCEPTANCE PREPROD PROD Project Server [1..N] 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 and managed by a release manager.

16 Demo!!!!

17 Demo Setup (One Repository) DEV1 PREPROD Fewer Queues DEV2 Automatic deployment Source code is in Git 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 and managed by a release manager.

18 About Gerger Hundreds of customers in 30+ countries. Gitora Manage your PL/SQL code with Git Contact me for a free consultation: yalim.gerger@gerger.co