pipeline {
agent any
stages {
stage('checkout') {
steps {
git 'https://github.com/rmpestano/tdc-pipeline.git'
}
}
stage('build') {
steps {
sh 'mvn clean package'
}
}
}
}JavaEE Pipeline as code using Jenkins, Docker and Sonar
Rafael Pestano
Software Engineer at PROCERGS
See this presentation in PDF here.
Continuous delivery
"A software strategy that enables organizations to deliver new features to users as fast and efficiently as possible"
Be readyto delivery in production at any moment!
Why?
"… If it hurts, do it more frequently, and bring the pain forward."
— Jez Humble
Goals
Reduce the risk of delivering
Create a well known delivery process/cycle
Make release process painless and without surprises
Be ready to go to production at anytime
Deploy to production
Principles
Each commit/push creates a release canditate
“The longer you delay, the worse(exponentially) the problem becomes“ [Neal Ford - Director at ThoughtWorks]
-
Heavily based on automation
-
Automated tests are primordial
-
Continuous and fast feedback (from end user as well from your release process)
Principles
-
Continuous improvement
-
Colaboration, everyone is responsible for the release process ( DEV, QA, OPs...)
-
Measurable progress
-
How many builds have failed?
-
In which stage it failed?
-
How long it takes to go to production?
-
Consequences
Less severity and frequency of failures related to a release
Reduced time to recovery from failures (MTTR)
Deployment pipeline
"… A pipeline is a set of stages to bring funcionality from developers to end users"
Jenkins 1.x pipeline
Jenkins 2.x pipeline
Jenkins 2.x pipeline
Described in a very easy and powerful DSL
Lives on source code (versioning)
Reuse with
shared librariesEverything in one place (Jenkinsfile)
Recovery from restarts
Jenkins 2.x pipeline as code
Jenkins 2.x pipeline on code
Jenkins 2.x pipeline on code
pipeline {
agent any
stages {
stage('build') {
steps {
sh 'mvn clean package'
}
}
stage('Deploy') {
steps {
sh 'docker stop tdc-pipeline || true && docker rm tdc-pipeline || true'
sh 'docker build -t tdc-pipeline .'
sh 'docker run -d --name tdc-pipeline -p 8181:8080 -v ~/db:/opt/jboss/db tdc-pipeline'
}
}
}
}Sonar
Sonar
pipeline {
agent any
stages {
stage('build') {
steps {
sh 'mvn clean package -DskipTests'
}
}
stage('unit-tests') {
steps {
sh 'mvn test -Pcoverage'
}
}
stage("SonarQube analysis") {
steps {
withSonarQubeEnv('sonar') {
sh 'mvn sonar:sonar'
}
}
}
stage('Deploy') {
steps {
sh 'docker stop tdc-pipeline || true && docker rm tdc-pipeline || true'
sh 'docker build -t tdc-pipeline .'
sh 'docker run -d --name tdc-pipeline -p 8181:8080 -v ~/db:/opt/jboss/db tdc-pipeline'
}
}
}
}Quality Gate
Quality Gate
pipeline {
agent any
stages {
stage('build') {
steps {
sh 'mvn clean package -DskipTests'
}
}
stage('unit-tests') {
steps {
sh 'mvn test -Pcoverage'
}
}
stage("SonarQube analysis") {
steps {
withSonarQubeEnv('sonar') {
sh 'mvn sonar:sonar'
}
}
}
stage("Quality Gate") {
steps {
sh 'sleep 12s'
timeout(time: 5, unit: 'MINUTES') {
script {
def result = waitForQualityGate()
if (result.status != 'OK') {
error "Pipeline aborted due to quality gate failure: ${result.status}"
} else {
echo "Quality gate passed with result: ${result.status}"
}
}
}
}
}
stage('Deploy') {
steps {
sh 'docker stop tdc-pipeline || true && docker rm tdc-pipeline || true'
sh 'docker build -t tdc-pipeline .'
sh 'docker run -d --name tdc-pipeline -p 8181:8080 -v ~/db:/opt/jboss/db tdc-pipeline'
}
}
}
}Post actions
pipeline {
agent any
//stages
post {
always {
sendNotification(currentBuild.result)
}
success {
echo 'Build was a success'
}
failure {
echo 'Build failure'
}
changed {
echo 'Build status changed.'
}
}
}//end pipeline
def sendNotification(buildStatus) {
buildStatus = buildStatus ?: 'SUCCESSFUL'
def color = buildStatus == 'SUCCESSFUL' ? 'good' : 'danger'
def message = "${currentBuild.fullDisplayName} *${buildStatus}*. (<${env.BUILD_URL}|Open>)"
slackSend (channel: '#builds', color: color, message: message)
}TDC Pipeline final
Video
Perguntas?
References
