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
Building a Jenkins Continuous Integration Pipel...
Search
Alexandru Zbarcea
October 19, 2016
Technology
3
350
Building a Jenkins Continuous Integration Pipeline with Docker
Alexandru Zbarcea
October 19, 2016
Tweet
Share
More Decks by Alexandru Zbarcea
See All by Alexandru Zbarcea
Continuous Delivery - Challenges in a Private Datacenter
azbarcea
1
190
Other Decks in Technology
See All in Technology
フレームワークを意識させないワークショップづくり
keigosuda
0
230
現場データから見える、開発生産性の変化コード生成AI導入・運用のリアル〜 / Changes in Development Productivity and Operational Challenges Following the Introduction of Code Generation AI
nttcom
1
420
LLMプロダクトの信頼性を上げるには?LLM Observabilityによる、対話型音声AIアプリケーションの安定運用
ivry_presentationmaterials
0
740
初めてのDatabricks Apps開発
taka_aki
1
230
Introduction to Sansan Meishi Maker Development Engineer
sansan33
PRO
0
310
会社を支える Pythonという言語戦略 ~なぜPythonを主要言語にしているのか?~
curekoshimizu
1
260
OSSで50の競合と戦うためにやったこと
yamadashy
3
880
[2025年10月版] Databricks Data + AI Boot Camp
databricksjapan
1
230
ソースを読むプロセスの例
sat
PRO
15
9.7k
AI-Readyを目指した非構造化データのメダリオンアーキテクチャ
r_miura
1
270
Implementing and Evaluating a High-Level Language with WasmGC and the Wasm Component Model: Scala’s Case
tanishiking
0
160
Digitization部 紹介資料
sansan33
PRO
1
5.6k
Featured
See All Featured
Designing for Performance
lara
610
69k
RailsConf 2023
tenderlove
30
1.3k
Typedesign – Prime Four
hannesfritz
42
2.8k
YesSQL, Process and Tooling at Scale
rocio
173
14k
jQuery: Nuts, Bolts and Bling
dougneiner
65
7.9k
Docker and Python
trallard
46
3.6k
Measuring & Analyzing Core Web Vitals
bluesmoon
9
630
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
55
3k
Testing 201, or: Great Expectations
jmmastey
45
7.7k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
37
2.6k
Principles of Awesome APIs and How to Build Them.
keavy
127
17k
Making Projects Easy
brettharned
120
6.4k
Transcript
Building a Continuous Integration Pipeline with Docker Alex Zbarcea -
Apache Committer (
[email protected]
, in/azbarcea, @azbarcea)
ABOUT THIS PRESENTATION Continuous Delivery
Business is a System inputs outputs feedback
Business is a System
Jenkins Artifacts Jenkinsfile + artfifacts artifacts
remote API dckr01 remote API dckr02 tutum jenkins archiva registry
nexus Jenkins Builds
Automated Service Operations App App Vault Nexus Internal on-premise services
Customer facing services github Continuous Integration Pipeline
The Machine to build the Machines
Computer architecture
None
None
rhel tomcat java app Another Distro One package manager -
automated patches Reuse Isolated app. One hierarchy security Conf. Mngt.
Artifacts .jar .war .npm .pip .apk .deb .rpm .docker .-box.tar.gz
.git - Chef - Ansible - .docker compositions - Pods .wiki .swagger.json apps/libs OS node config. docs .docker .docker compositions .rancher compositions only markdown (text) artifacts are allowed
Demo
Challenges
Pipeline Challanges - everybody sees and understands the pipeline -
optimize for the global scope - inventory of INs and OUTs - artifact warehouse management - containerize everything
- Not all image can be build in docker-in-docker (dind)
- Caching artifacts (e.g.: /.m2/repository folder) - Use data containers Docker Challanges
Operations Challenges - FAIL is good. Trust the upgrade button
- complexity - generates: lack of trust - difficult to investigate - .git/social becomes a core system - emergent properties - focus is on scaling - deployments as a non-event
Thank you MCJUG apifocal