Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Continuous Delivery in Java - Things we learned hurting ourselves
Search
Paolo D'Incau
November 07, 2015
Programming
0
34
Continuous Delivery in Java - Things we learned hurting ourselves
The slides of my talk at the Italian Agile Day 2015 about Continuous Delivery in Java
Paolo D'Incau
November 07, 2015
Tweet
Share
More Decks by Paolo D'Incau
See All by Paolo D'Incau
Exploring Processes and OTP behaviours in Erlang
pdincau
2
270
Other Decks in Programming
See All in Programming
DocC Tutorial と TCA におけるテスト機能の紹介
kalupas226
1
330
孤独のCTOグルメという やや奇抜な企画をやった目的と効果
shoheimitani
3
1k
プロンプトエンジニアリング入門
tomokusaba
2
970
AppDeveloperCon 2024 EU: Building polyglot developer experiences in 2024
salaboy
0
380
SwiftUI, Jetpack Composeの導入で変化した「家族アルバム みてね」のアプリ開発体験
hicka04
6
400
Prepare for Jakarta EE 11 - Performance and Developer Productivity
ivargrimstad
0
490
RubyVM を PHP で実装する 〜Hello World を出力するまで〜
memory1994
PRO
1
490
Open Source Swift Workshop - Foundation and first party libraries
ikesyo
0
180
導入から5年が経って見えた Datadog APM 運用の課題
bgpat
2
540
htmx is fun!
codehex
2
190
MySQL のインデックスの種類をおさらいしよう! / overviewing indexes in MySQL
okashoi
0
170
Introduction for Open Source Swift Workshop
giginet
PRO
0
180
Featured
See All Featured
Git: the NoSQL Database
bkeepers
PRO
421
63k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
226
16k
Bash Introduction
62gerente
604
210k
Build The Right Thing And Hit Your Dates
maggiecrowley
23
1.9k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
501
140k
Designing on Purpose - Digital PM Summit 2013
jponch
109
6.4k
Designing Experiences People Love
moore
135
23k
Practical Orchestrator
shlominoach
180
9.7k
Making the Leap to Tech Lead
cromwellryan
123
8.4k
Code Reviewing Like a Champion
maltzj
512
39k
GraphQLの誤解/rethinking-graphql
sonatard
48
9.1k
The World Runs on Bad Software
bkeepers
PRO
60
6.6k
Transcript
Continuous Delivery in Java Cose che abbiamo imparato facendoci del
male Italian Agile Day ‘15
@pdincau Here I am
Continuous Delivery? What is
“Continuous Delivery is a software development discipline where you build
software in such a way that the software can be released to production at any time. ” Martin Fowler* * martinfowler.com/bliki/ContinuousDelivery.html
“Continuous Delivery is nothing more than reducing the stress you
get when you deliver business value to the customer ” My Team* * Come and ask!
n t Continuous Delivery... What is
Continuous Integration
Continuous Deployment
“Safety" Deploy rules
Technically Speaking
Deploy any specific working version to production with confidence
3 ways
Rodeo Style
No tests Manual deploy Snowflake environments Non predictable outcome Few
or very little collaboration
By the book
Fast Feedback Done is released Shared responsibility Everything is automated
Repeatable and reliable process
Start small and iterate
Once upon a time...
We did know...
Previous deployment process was painful Database continuously change Different environments
Iteration n.1 No Automation
Environment replica on AWS Manual build Manual DB migrations Deploy
with scp to remote JBoss
It was our own choice...
...but we felt like this
No automation at all When was our last deploy?
A taste of Automation Iteration n.2
Set up a basic Jenkins installation Test and build triggered
on push DB migration using Liquibase Task to deploy on AWS
This worked for a while
Errors in MyBatis DB mappers Wrong/Missing wirings
Yay! Environments are ready!
Deploy Everywhere Iteration n.3
New Jenkins job to run IT Track slowest tests First
official deploy an all environments
…with different DB drivers !#$?!
Duplication
Incorrect use of mvn profiles N-builds for N-environments Long build
and deploy time
Single Artefact Iteration n.4
Got rid of configurations using JBoss *Unique* artefact for all
environments Deploy version X.Y.Z from Nexus
We started getting fast
But QA were not so happy Branches, branches everywhere!
Make them happy Iteration n.5
AWS is for nightly builds Tags over branches Track deployed
version
Acceptance tests
Explained values and motivations to Product Owner
Remove Candidate Clean Up Clean Up Meet the pipeline Migrate
Database Fetch Unit Tests Build Build Slow Tests Integration Tests Integration Deploy Publish UAT QA and Publish
Where to go next
Parallel builds Environments Provisioning
Things we would change...
Pipeline with “placeholders” Extract configurations Explain at the beginning the
values behind
Things we would do again...
Build the pipeline iteratively Use of Liquibase Share pipeline responsibility
Recommended reading
That’s all!
Thanks @pdincau