Presentation about using Jenkins as an automation tool for deploying database objects and APEX Applications. Jenkins Pipelines are used and compared to Jenkins Jobs.

1. Jenkins Pipeline
meets Oracle
Oliver Lemm
Rotterdam, 26-MAR-2019
enabling the adaptive enterprise

2. Key Facts
Independent Technology House
with Cross-Industry Expertise
Headquarter
Ratingen
230 employees
Founded
1994
Top Company for Trainees &
Students
Privately-Owned
Corporation
Oracle Platinum
Partner
Microsoft Gold
Partner33 Mio. Euro
Revenue in 2018
Germany‘s number
1 in APEX
Branches
Frankfurt & Cologne
2

3. 3
about me
 Oliver Lemm, Business Unit Leader APEX
 Born 1980, married, four Children, Place of Residenz Dinslaken
 since 2.2007 at the MT AG in Ratingen
 Working with APEX since 2007
 Leading in Distribution/Marketing/Delivery for APEX Projects
 https://apex.mt-ag.com
 Doing presentations at DOAG Conference, APEX World, DOAG APEX Connect & ODTUG
KScope

4. 1. Introduction in Jenkins
2. What is a Pipeline
3. Creating a Pipeline
4. Jenkinsfile
5. Moving from Jenkins Jobs to Pipeline
6. Complex Pipeline
7. After Jenkins Pipeline
4
Agenda

5. 5
https://jenkins.io/
Jenkins

6. “a leightweight tool which is a GUI for your automated processes”
“used for continuous integration and continuous delivery”
“easy to integrate version control”
“free software”
“can be compared with gitlab or atlassian bamboo”
6
what is Jenkins?

7. Job
“declarative” defined process
build step
calling a batch or running a single http request
one or more build steps are part of a job
Build
every time running a process results in a Build
7
keywords in Jenkins …

8. 8
Demo

9. exporting & importing APEX applications
generating patchfiles for your application/schema objects
using datapump
running backend & frontend tests
creating users, tablespaces, grants
deploying scripts to different databases
9
using Jenkins in Oracle for …

10. defining one or multiple jobs in a script
Domain Specific Language (DSL)
pipeline output
10
what is Pipeline?

11. durable
pausable
versatile
extensible
versionable
11
advantages of pipeline are …
comparing Pipeline vs Job

12. 12
new item “pipeline”
creating a pipeline (1)

13. 13
creating a pipeline (2)

14. pipeline {
agent {
label {
label ""
customWorkspace "C:/jenkins_projects/cicd"
}
}
stages {
stage('Export APEX App') {
steps {
withCredentials([usernamePassword(credentialsId: 'db_schema_demo_dev',
passwordVariable: 'db_schema_pw', usernameVariable: 'db_schema_user')]) {
bat '''cd trunkapex
..batchexport_apex_app_sqlcl %db_schema_user% %db_schema_pw% pdb1 %app_id%'''
}
}
}
}
14
simple example
Jenkinsfile

15. agent any
agent none
agent { label “windows” }
agent {
customWorkspace “c:/Jenkins_projects/cicd”
}
agent {
docker {
image “maven:3-alpine”
}
}
15
agent
Jenkinsfile
1) all stages / steps will run on any agent
2) each stage will run on it’s own agent
3) for parallel processes multiple agents can
be used and named
4) running jobs in a special workspace the
agent should be defined with a
customWorkspace
5) using docker you can define different
environments based on docker images

16.  every pipeline must be defined in stages
 every “stages” can have 1-x stage
 a stage is a functional bracket
 every stage is visible in the Jenkins output
16
stage / stages
Jenkinsfile
stages {
stage ("Prepare") { ... }
stage("PROD - Export App") { ... }
stage("PROD - Datapump Export") { ... }
stage("Move Dumps") { ... }
stage("TEST - Delete Old DB Objects") { ... }
stage("TEST - Datapump Import") { ... }
stage("TEST - Import App") {...}
}

17.  a step is a technical “bracket”
 a step is inside a stage
 every stage can have 1-x steps, mostly one stage
has 1 step
 a step can be a batch or shell or even a plugin call
https://jenkins.io/doc/pipeline/steps/
17
step
Jenkinsfile
stages {
stage(“run my batch“) {
steps {
bat '''export_apex_app_sqlcl'''
}
}
}

18. 18
Snippet Generator
Jenkinsfile

19.  using passwords in a save way
 passwords itself are safed encrypted inside Jenkins
 credentials are only useable inside the “brackets”
 the password ID should be defined and not a random given number
 passwords are not readable inside the command line
19
credentials
Jenkinsfile
steps {
withCredentials([usernamePassword(credentialsId: 'db_schema_demo_dev',
passwordVariable: 'db_schema_pw',
usernameVariable: 'db_schema_user')]) {
bat '''cd trunkapex
..batchexport_apex_app_sqlcl %db_schema_user% %db_schema_pw% pdb1 %app_id%'''
}
}

20. 20
database or other technical users
Credentials

21.  searching for error after each stage
 setting build “FAILURE”, “UNSTABLE” or “SUCCESS”
21
errorhandling by stage
Jenkinsfile
stage("Create Grants and Synonyms") {
steps {
bat 'REM Create Grants and Synonyms STARTED'
bat '''batchcreate_grants_synonyms'''
bat 'REM Create Grants and Synonyms FINISHED'
script {
String[] errors = ["ORA-"]
checkConsoleOutputAfterBuildStep("Create Grants and Synonyms STARTED",
"Create Grants and Synonyms FINISHED", errors,
"Create Grants and Synonyms Failed!", "FAILURE")
}
}
}

22.  Post processing after
every stage
 Overall one post
processing at the end of
the pipeline
22
errorhandling by pipeline
Jenkinsfile
pipeline {
stages {
stage('do something') { …
post {
success { bsNotifySuccessful("Set up Jobcontrol Environment") }
unstable { bsNotifyUnstable("Set up Jobcontrol Environment") }
aborted { bsNotifyAborted("Set up Jobcontrol Environment") }
failure { bsNotifyFailed("Set up Jobcontrol Environment") }
}
}
post { success { notifySuccessful() }
unstable { notifyUnstable() }
aborted { notifyAborted() }
failure { notifyFailed() }
}
}
}

23.  running steps by condition
 using conditions for environments
23
conditional
Jenkinsfile
stage(‘conditional by environment') {
agent label:'test-node' when {
environment name: 'NAME', value: 'this'
}
steps {
echo 'run only if the env name and value
matches'
}
}

24. 24
start from stage
Pipeline

25.  is groovy code
 validate code with pipeline Linter
25
Jenkinsfile

26. pipeline {
agent {
label {
label "„
customWorkspace "C:/projects/uit_fpp/svn„
}
}
stages {
stage('110 - Drop Users and Tablespaces') {
steps {
script {
def drop_users_and_tablespaces = build job: '110_drop_users_and_tablespaces',
parameters: [string(name: 'environment', value: "${params.environment}"),
string(name: 'start', value: 'Ja')]
currentBuild.result = drop_users_and_tablespaces.result
}
}
}
stage('120 - Create Users and Tablespaces') { … }
}
}
26
pipeline starting standard Jenkins jobs
moving from Jobs to Pipeline

27. 27
overview
Looking into a complex scenario
DEMO

28. 28
logs by stage
Looking into a complex scenario

29. 29
build history, trend and timeline
Looking into a complex scenario

30.  … more flexible
 … code
 … versionable
 … not declarative any more
 … still jenkins
30
Pipeline is
Conclusion
pictures by Jenkins.io

31. 31
Blue Ocean - https://jenkins.io/projects/blueocean/
and after Pipeline (1)

32. 32
Jenkins X
and after Pipeline (2)
https://jenkins.io/projects/jenkins-x

33. 33
APEX Migration Workshop - https://apex.mt-ag.com/apex/f?p=276:3
… after APEX World (1)

34. 34
APEX Connect 2019 - https://apex.doag.org
… after APEX World (2)

35. @OliverLemm
https://www.linkedin.com/in/oliverlemm
https://www.xing.com/profile/Oliver_Lemm
https://oliverlemm.blogspot.com/
enabling the adaptive enterprise