Jenkins Pipelines Advanced
0 likes857 views
The document presents an overview of Jenkins pipelines, emphasizing their advantages such as durability, versatility, and versioning. It includes practical examples of creating pipelines with Jenkinsfiles, error handling, and managing multiple environments. Additionally, it highlights integration with unit testing and the generation of release files for deployments.
![10
Jenkinsfile
simple example
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%'''
}
}
}
}](https://image.slidesharecdn.com/2019jenkinspipelinesadvanced-191121200923/85/Jenkins-Pipelines-Advanced-9-320.jpg)
![13
Pipelines & Jobs
Jobs are reuseable in pipelines
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') { … }
}
}](https://image.slidesharecdn.com/2019jenkinspipelinesadvanced-191121200923/85/Jenkins-Pipelines-Advanced-12-320.jpg)
![15
Passwords
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%''‚
}}}
stage('Commit to trunk') {
steps {
withCredentials([usernamePassword(credentialsId: '8a1d2bde-19e2-4a63-be00-f1145a8bdfe3',
passwordVariable: 'svn_password', usernameVariable: 'svn_username')]) {
bat '''cd trunkapex
svn --username=%svn_username% --password=%svn_password% add f%app_id%.sql –force
svn --username=%svn_username% --password=%svn_password% commit -m "automatic commit from
Jenkins" f%app_id%.sql''‚
}}}
with Credentials Binding Plugin](https://image.slidesharecdn.com/2019jenkinspipelinesadvanced-191121200923/85/Jenkins-Pipelines-Advanced-14-320.jpg)
![17
Errorhandling
stage("Install all QS Packages") {
steps {
bat 'REM -----Install all QS Packages STARTED-----'
bat '''cd trunk
batchinstall_qs_objects batchaccount_data_%environment%.txt''‚
bat 'REM -----Install all QS Packages FINISHED-----'
script {
String[] errors = ["ORA-", "SP2-"]
String[] warnings = ["WARNING"]
checkConsoleOutputAfterBuildStep("-----Install all QS Packages STARTED-----",
"-----Install all QS Packages FINISHED-----",
errors, "Install all QS Packages Failed!", "FAILURE")
checkConsoleOutputAfterBuildStep("-----Install all QS Packages STARTED-----",
"-----Install all QS Packages FINISHED-----",
warnings, "Install all QS Packages has warnings!", "UNSTABLE")
}}}
custom plugin](https://image.slidesharecdn.com/2019jenkinspipelinesadvanced-191121200923/85/Jenkins-Pipelines-Advanced-16-320.jpg)
Jenkins Pipelines Advanced
- 1. 1 Oliver Lemm - DOAG 2019 Jenkins Pipelines Advanced
- 2. 2 Unsere Hard Facts Zertifizierter Partner von Oracle Microsoft 280 Beschäftigte Inhabergeführt Ausbildungsbetrieb Partner im dualen Studium Branchen- übergreifend Herstellerneutral Hauptsitz Ratingen Niederlassungen Frankfurt am Main Köln Dortmund München Gründung 1994 33 Mio. Euro Umsatz >100 Kunden Ihr Partner für den digitalen Wandel Individuelle IT-Lösungen aus einer Hand
- 3. 4 Oliver Lemm • Business Unit Leader APEX @ MT AG • Architect, Project Leader, Developer
- 4. 5 Agenda • Jenkins Pipelines • Jenkinsfile • Best Practices • Future
- 5. 6 what is a Pipeline? doing multiple steps in one “job” Domain Specific Language (DSL) pipeline output
- 6. 7 pipeline vs standard Job durable - robust advantages of pipeline are pausable - pausierbar versatile - vielseitig extensible - erweiterbar versionable - versionierbar
- 7. 8 creating a pipeline (1) new Item „pipeline“
- 8. 9 creating a pipeline (2)
- 9. 10 Jenkinsfile simple example 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%''' } } } }
- 10. 11 Jenkinsfile output pipeline { agent {…} stages { stage('Export APEX App') {…} stage('Commit to trunk') {…} stage('Import APEX App') {…} } }
- 11. 12 Jenkinsfile vs inline script both • groovy Syntax Jenkinsfile • Versionable • reuseable Script • Snippet Generator • easier to use
- 12. 13 Pipelines & Jobs Jobs are reuseable in pipelines 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') { … } } }
- 13. 14 Workspace / “Arbeitsbereich” • one repository by project • less space • less traffic • faster • Workspace not below “jobs” … agent { label { label "" customWorkspace "C:/jenkins_projects/cicd" } } …
- 14. 15 Passwords 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%''‚ }}} stage('Commit to trunk') { steps { withCredentials([usernamePassword(credentialsId: '8a1d2bde-19e2-4a63-be00-f1145a8bdfe3', passwordVariable: 'svn_password', usernameVariable: 'svn_username')]) { bat '''cd trunkapex svn --username=%svn_username% --password=%svn_password% add f%app_id%.sql –force svn --username=%svn_username% --password=%svn_password% commit -m "automatic commit from Jenkins" f%app_id%.sql''‚ }}} with Credentials Binding Plugin
- 15. 16 Errorhandling basic findText regexp: '<regular expression>', fileSet: '<file set>‘ check the console log: findText regexp: '<regular expression>', fileSet: '<file set>', alsoCheckConsoleOutput: true only check console: findText regexp: '<regular expression>', alsoCheckConsoleOutput: true mark success, warning or failure use succeedIfFound, unstableIfFound, or notBuiltIfFound: findText regexp: '<regular expression>, alsoCheckConsoleOutput: true, unstableIfFound: true with Text Finder plugin (since Version 1.11)
- 16. 17 Errorhandling stage("Install all QS Packages") { steps { bat 'REM -----Install all QS Packages STARTED-----' bat '''cd trunk batchinstall_qs_objects batchaccount_data_%environment%.txt''‚ bat 'REM -----Install all QS Packages FINISHED-----' script { String[] errors = ["ORA-", "SP2-"] String[] warnings = ["WARNING"] checkConsoleOutputAfterBuildStep("-----Install all QS Packages STARTED-----", "-----Install all QS Packages FINISHED-----", errors, "Install all QS Packages Failed!", "FAILURE") checkConsoleOutputAfterBuildStep("-----Install all QS Packages STARTED-----", "-----Install all QS Packages FINISHED-----", warnings, "Install all QS Packages has warnings!", "UNSTABLE") }}} custom plugin
- 17. 18 Support multiple Environments One Pipelinejob for multiple instances • only one pipeline to maintain One Pipelinejob for every instance • less parameters • automation possible • see when last time the environment was updated • see which environment is successfully patched one Jenkinsfile is used for …
- 18. 19 Parameters • Impdp_source_environment => which base datapump file to use? • Version => which version to install? • Impdp_version => what is the version of the dataump file? • run_install_script_pre_version => any script which has to run after import the dump`?
- 19. 20 Logs • logs are generated every installation • logs are save inside Source Control Management • logs are related to the release • logs are also saved when installation is not done by jenkins • logs must be saved even when Jenkins Pipeline is broken
- 20. 21 utPLSQL • utPLSQL is used for Unit Testing http://utplsql.org/ • One job by every bigger component • utPLSQL will generate an XML Output • Use Post-build Action to generate one XML File based on the output • Use Publish Junit test result report for generating the Test Result
- 21. 22 Build a Release File • Customer needs an installationfile => one ZIP-Archive • ZIP-Archive will be add to VCM (Artifact) • Installation without Jenkins is needed • Parameters for Databases must be added • Parameters for Development/Testing environments are removed • Further checks only for developer purposes are removed • Release Notes will be generated
- 22. 23 GoDevOps Conference in 2020 will come
- 24. News from the MT Lab: APEX Testing Framework • APEX metadata-driven User Acceptance Tests • Execute on many different test engines (Selenium, browserstack.com, Puppeteer, etc.) • Demo Video: https://bit.ly/apextesting • Contacts: • Kai Donato • Fabian Neureiter 1. Get APEX 2. Create testcases3. Schedule/Run testcases
- 25. 26 ? Vielen Dank für die Aufmerksamkeit! Fragen oder Diskussionsbeiträge