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 Pipeline with Docker
Search
Alexandru Zbarcea
October 19, 2016
Technology
3
320
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
170
Other Decks in Technology
See All in Technology
エンジニア候補者向け資料2024.04.24.pdf
macloud
0
3.3k
20分で完全に理解するGrafanaダッシュボード
hamadakoji
3
350
継続的な改善 x ⾮連続的な進化
sansantech
PRO
3
150
アクセス制御にまつわる改善 / Improving access control
itkq
0
530
プラットフォームってつくることより計測することが重要なんじゃないかという話 / Platform Engineering Meetup #8
taishin
1
350
MLOpsの「壁」を乗り越える、LINEヤフーの Data Quality as Code
lycorptech_jp
PRO
5
470
ExaDB-D dbaascli で出来ること
oracle4engineer
PRO
0
2.1k
AOAI をきっかけに 社内の Azure 管理を見直した話
recruitengineers
PRO
1
260
Kernel MemoryでAzure OpenAI Serviceとお手軽データソース連携
mitsuzono
1
240
ユーザーストーリーのレビューを自動化したみたの
bun913
1
420
コンパウンドスタートアップのためのスケーラブルでセキュアなInfrastructure as Codeパイプラインを考える / Scalable and Secure Infrastructure as Code Pipeline for a Compound Startup
yuyatakeyama
4
4.7k
Postman v10リリース後を振り返る / Looking back at Postman v10 after release
yokawasa
1
160
Featured
See All Featured
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
121
39k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
30
6k
In The Pink: A Labor of Love
frogandcode
138
21k
Debugging Ruby Performance
tmm1
70
11k
Optimising Largest Contentful Paint
csswizardry
8
2.4k
Docker and Python
trallard
34
2.7k
What’s in a name? Adding method to the madness
productmarketing
PRO
16
2.6k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
125
32k
A better future with KSS
kneath
231
16k
BBQ
matthewcrist
80
8.8k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
226
51k
GraphQLとの向き合い方2022年版
quramy
32
12k
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