APEX 5, JSON, REST & Jira

39 Pages·2016·3.42 MB·English

How to use Version
Control in APEX projects?
Oliver Lemm
APEX Connect
26.04.2016
Facts & Figures
Headquarter
240
Ratingen
Employees
(North Rhine – Westphalia)
Independent Technology House
with Cross-Industry Expertise
Privately- Oracle
24 Mio. Euro Founded
Owned Platinum
Revenue 1994
Corporation Partner
Top Company Branches
for Trainees & Dortmund, Cologne,
Students Frankfurt
2
about me
 Oliver Lemm
 since february 2007 working for MT AG in Ratingen
 Competence Center Leader APEX & Service Center Leader APEX
 Diploma applied computer science at the university of Duisburg-Essen
 Projectleader, IT-Architect and Developer
 working with Oracle Databases and Oracle Application Express since 2007
 Blog http://oliverlemm.blogspot.de
 Twitter https://twitter.com/OliverLemm
3
Agenda
1. Motivation
2. Version Control
3. Versioning APEX Application
4. Versioning Database Objects
5. Versioning external Files
4
Motivation
5
Motivation
„make it visible what has changed, who changed it and when was the change“
„create a snapshot of the whole scripts of a delivered software“
„define a central repository for the code“
„make it possible to automate testing and deployment“
6
Version Control
Version Control
Revision
Source Control
Control Source Code
Management
Files
Numbers
„SCM“ Software
Configuration
Management
7
Version Control
software history
 proprietary and local
 PVCS since 1985
 Open Source & Client Server
 CVS since 1986
 Subversion / SVN since 2000
 Distributed
 Git since 2005
 GitHub – web-based Git repository
8
Version Control
Subversion
working directory
 you need a repository server
 direct commit into repository
repository
 revision and version central
 version history only on server
 Central approach supports security and rights management
9
Source Control
keywords
commit merge diff update
trunk tag branch
10