gitora, version control for pl/sql
TRANSCRIPT
Version Control for PL/SQL
• About the Company
• What is the problem?• How does Gitora help?
• Demo!!• How does Gitora work?
About Gerger
Gitora Tool to manage your PL/SQL code base with Git. www.gitora.com
Formspider Application development framework for Oracle PL/SQL developers. First Class Web and Mobile Applications with only PL/SQL as the programming language. www.theformspider.com
We help Oracle customers catch up to modern technology.
Hundreds of customers in 30+ countries. Offices in California, US and Istanbul, Turkey.
(Formerly ING Insurance).
Turkish Telco.
Germany
US. Global manufacturer of equipment used in product assembly.
Argentina. Government of Rio Negro. Forms Modernisation.
United Kingdom NetherlandsUS Fortune 5 Company
Lithuania
ItalyGreece
Germany
Italy
Peru. Financial Systems
Russia. Metkombank
Russia
Azerbaijan. Core Banking
Czech Republic .Logistics ERP
Every team created its own “system” that sort of kind of works until it doesn’t.
Version Control is a difficult topic to talk about in the PL/SQL Community.
Common version control tools are not available to PL/SQL developers.
Lack of proper version control is one of the top reasons IT shops avoid coding with PL/SQL.
We can’t work as productively as other developers.
We can’t deploy as fast as other developers.
We can’t respond to changes in business as quickly as other developers.
Moving code is more error prone.
We can’t work together like other developer do.
We loose code more often.
It is harder for us to test our code automatically.
Apply common version control commands such as merge, branch, reset to the code in the database. (The PL/SQL in the DB changes automatically.)
Gitora 2.0 enables you to:
Commit changes to PL/SQL objects to Git.
Lock PL/SQL objects in the database (and still continue using your favourite PL/SQL editor.)
Move your changes between databases automatically.
Manage packages, functions, procedures, views, triggers, synonyms and object types in Git
Customer SpotlightSuccess Story:
Manages over 20,000 database objects
Rhenus Logistics, leading logistics service company from Germany, uses Gitora.
Database objects are spread over 30+ schemas
System Architect/Team Lead Michiel Arentsen blogs about Gitora at: http://michielarentsen.blogspot.com/
Implementing version control with Gitora is the least risky, most beneficial and the most cost effective way to improve your teams productivity.
Risk: What’s the worst that can happen?
Benefits: Up to 10x productivity. Up to 95% fewer errors during deployment.
Cost: 169 per developer
Traditional PL/SQL Development
Queued access
Blocking
Interrupting
DEV RELEASE TEST INTEGRATION QA
Manual deployment
USER ACCEPTANCE PREPROD PROD
Intermingled projects, features, hot fixes
Practically impossible to branch, merge
Developers are expected to follow version management rules manually.
Version control repo is a last resort back up
or any other version control system
1..n database servers
Manual
No automated testing
PL/SQL Development with Gitora Step 1 (One Repository)
Queued access
Blocking
Interrupting
DEV
Automatic deployment
USER ACCEPTANCE HOTFIX
PREPROD PROD
Intermingled projects, features
Basic branching and merging is possible for hot fixes
Version control rules are enforced at the DB level and managed by a release manager.
Source code is in Gitora
Automatic Script Generation with Gitora
Person responsible for releases (manages all code in all Database Instances)
RELEASE TEST INTEGRATION QA
Development on DEV only. On some other DB’s bug fixes may be allowed.
Faster hot fixes Better automatic testing
PL/SQL Development Step 2 with Gitora (One Repository)
Fewer Queues
Less Blocking
Less interruption
DEV1
Automatic deployment
PROD
Less intermingled projects, features
Basic branching and merging is possible
Version control rules are enforced at the DB level and managed by a release manager.
Source code is in Gitora
Automatic DDL Script Generation with Gitora
Person responsible of releases (manages all code in all Database Instances)
RELEASE TEST HOTFIX INTEGRATION QA USER ACCEPTANCE PREPROD
Hot fixes delivered faster
DEV2N DEV servers DEV1, DEV2, DEV3,…DEVN
Better automatic testing
Development on DEV only. On some other DB’s bug fixes may be allowed.
PL/SQL Development Step 3 with Gitora: Implement Any Git Workflow (One Repository)
No Queues
No Blocking
No Interruptions
Automatic deployment
PROD
No blocking between projects, features
Branching and merging is possible
Version control rules are enforced at the DB level and managed by a release manager.
Source code is in Gitora
Automatic DDL Script Generation with Gitora
Person responsible of releases (manages all code in all Database Instances)
RELEASE TEST HOTFIX INTEGRATION QA USER ACCEPTANCE PREPROD
Faster hot fixes
Project Server [1..N]
RELEASE TEST INTEGRATION QA
Every developer works in a private environment. Each private environment can be switched to a branch.
Great automated testing
How does Gitora 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.
Only executes what’s changes in the DB. (Very fast!)
Gitora consists of a DB schema and some Java.
Show, Don’t Tell
Demo Setup (One Repository)
Fewer Queues
Less Blocking
Less interruption
DEV1
Automatic deployment
Less intermingled projects, features
Basic branching and merging is possible
Version control rules are enforced at the DB level and managed by a release manager.
Source code is in Gitora
Person responsible of releases (manages all code in all Database Instances)
PREPROD
Hot fixes delivered faster
DEV2
Better automatic testing
This can be any intermediate server between PROD and DEV