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
On our CI and Builds
Search
Nathan Kleyn
March 03, 2015
Programming
0
2.4k
On our CI and Builds
Presentation to internal Engineering team on exactly how our builds and CI work.
Nathan Kleyn
March 03, 2015
Tweet
Share
More Decks by Nathan Kleyn
See All by Nathan Kleyn
Distributed ID Generation
nathankleyn
1
2.2k
Semantic Versioning With Git
nathankleyn
2
330
Exception Handling
nathankleyn
0
97
Cucumber Automation Testing
nathankleyn
3
180
Git: Everything You Need To Know (And A Few More Things)
nathankleyn
3
130
How The VM Works
nathankleyn
0
100
Other Decks in Programming
See All in Programming
CSC307 Lecture 14
javiergs
PRO
0
220
リハビリmruby
kishima
1
160
Architectures with Lightweight Stores: New Rules and Options
manfredsteyer
PRO
0
100
みんなのオブザーバビリティプラットフォームを作ってるんだがパフォーマンスがやばい #mackerelio #srenext
ne_sachirou
0
380
継続的な活動で築く地方エンジニアの道
myamashii
2
360
最近追加した型の紹介とその振り返り
aki19035vc
0
180
HMSコンペ 11th Solution (team : kansai-kaggler)
t88
1
680
20240706_CDKConf
takuyay0ne
0
1.2k
データカタログ運用物語 〜令和6年夏の理想と現実〜
kuro_kurorrr
0
110
DynamoDB コスト最適化っぽいことの基本 with Terraform
kuro_kurorrr
2
250
Microservices rules (July 2024) : what good looks like
cer
PRO
0
1.6k
Jetpack for KMP
fornewid
1
290
Featured
See All Featured
Optimizing for Happiness
mojombo
373
69k
Building Your Own Lightsaber
phodgson
101
5.9k
Web Components: a chance to create the future
zenorocha
307
41k
Adopting Sorbet at Scale
ufuk
71
8.8k
Code Review Best Practice
trishagee
58
16k
A better future with KSS
kneath
231
17k
Designing with Data
zakiwarfel
96
5k
BBQ
matthewcrist
82
9k
Testing 201, or: Great Expectations
jmmastey
33
6.9k
Debugging Ruby Performance
tmm1
71
11k
Visualization
eitanlees
139
14k
Designing Experiences People Love
moore
136
23k
Transcript
On our CI and BUILDS HOW THEY WORK
Or: How shit gets built and deployed.
Builds involve:
GitHub ∙ CircleCI Ruby ∙ Thor Docker
And copious amounts of:
Swearing ∙ Fear Punching ∙ Hate Quiet Weeping
None
On the PROCESS OF BUILDING A COMMIT
The steps to build:
1. Make a commit.
2. Push to GitHub.
3. CircleCI is notified.
4. The build begins.
5. The Docker build begins.
6. The sanity build begins. (if master)
7. Deployment can begin.
On the PUSHING OF A COMMIT
GitHub receives your commit and dispatches a notification to CircleCI.
Cheers bro. Welcome blud. all of teh infos
CircleCI receives a payload of information telling it what commit
this was.
CircleCI starts a container up for the build.
Boom bitches.
It then looks for our circle.yml file.
Each step of this file is executed.
These steps execute a bunch of shell scripts in /circle.
These steps... ∙ Configure versions of software to use (Ruby,
Java, Kafka, HBase, etc). ∙ Restore the cache. ∙ Checkout the repository. ∙ Build all the projects. ∙ Test all the projects. ∙ Save all the artifacts to CircleCI.
We have three different kinds of builds:
Standard ∙ Docker Sanity
We tell it what scripts to use by passing a
MODE env var.
Demo: The CircleCI build scripts.
On the DOCKER BUILDS OUR CODE IN CONTAINERS
Quick Docker refresher:
Docker is built on the idea of containers.
Many container!
You build images. You deploy containers.
How it happens:
A second parameterised build is started for Docker.
These builds have whatever info they need passed as parameters.
It builds, tags and pushes the Docker images.
The building happens on a separate machine.
The pushed images are stored in the Docker registry.
When we deploy, we pull down these images and run
them (making containers!)
On BUILD SCRIPTS USING AND ABUSING THOR
Thor is a task framework.
I’m actually really sensitive and kind.
All of the things we do on CircleCI are Thor
tasks.
The Thor task sources are in /build-scripts/thor.
Each task is namespaced. thor foo:bar
You can get help for a task by running thor
help task.
All Thor tasks are just Ruby files. Thor is just
a nice DSL.
Demo: The Thor build scripts.
On COMMON PROBLEMS SOLVING COMMON ISSUES
Q: Gradle tasks hanging locally.
A: Start the Nexus server.
Q: Deployments fail as unable to pull from repository.
A: Start the Docker registry.
Q: Docker build fails with “no space left on device”.
A: Restart the Docker server, if it still fails call
for help.
Q: “Expected ID but got nil”.
A: (Sadly) Just retry the build. This is a Docker/library
bug that happens randomly.
Q: The tests are failing.
A: Your tests are shit. Fix your tests.
On BEING A BUILD EXPERT BECOME A ZOMG HACKER
Demo: How to find the build to deploy.
Demo: How to see what SHA is being built for
Docker.
Fin. I’m gonna eat your hairy legs.