Your Build is Probably Broken, you just don't know it yet

Modern software development needs a modern CI; the patterns you follow when developing your code should also be reinforced by your CI pipeline. No snowflakes. No unstable results. No unscalable bottlenecks. Everything as code.

We will discuss the patterns that we want a CI solution to follow and why they are important, especially, but not exclusively, in the pursuit of continuous delivery and the adoption of DevOps and PaaS. You should leave feeling optimistic that tomorrow you can use Concourse CI to regain control of your pipeline, dramatically increasing velocity and consistency and, most importantly, reduce the time it takes to deliver value to users and receive feedback.

Delivered at LoPUG: https://www.meetup.com/London-PaaS-User-Group-LOPUG/events/234263654/

Transcript

1. Your build is probably broken, you just don't know it yet
2. Broken? ▪ You don’t have one ▪ Your pipeline is unsecure ▪ Your pipeline is slow ▪ Your pipeline is unreliable or unreproducible ▪ Your pipeline is a time sink ▪ Your pipeline is not a core deliverable
3. Treat CI like code ▪ Development Lifecycle ▪ Fast feedback ▪ Zero-downtime ▪ Scalable & Instrumented ▪ Ephemeral ▪ Everything as code
4. Before ▪ Time consuming pipeline orchestration - Chef ▪ Bring your own automation - Jenkins Job Builder ▪ Polluted and inconsistent ▪ Performance & Cost ▪ Environment disparity ▪ Poor usability
5. Concourse CI What you might miss Plugins Being able to configure a gazillion plugins Runtime configuration Change the environment at build time Click-click-clicking Being able to use a GUI to configure build Not knowing BOSH Great tool, getting easier (BBL) with steep learning curve Not knowing Docker Docker is key and you’ll need a workflow to manage images Speed Isolated builds can be slower to initialise e.g. bundle install
6. Install ▪ Vagrant ▪ Docker Compose ▪ Standalone Binary ▪ BOSH [with BBL] e.g. bbl up http://concourse.ci/installing.html
7. Install Vagrant & fly Vagrant 3 minute Configuration 1 second View Up to you $ vagrant init concourse/lite $ vagrant up $ fly -t lite login -c http://192.168.100.4:8080 $ fly -t lite set-pipeline -p hello-world -c hello.yml http://192.168.100.4:8080
8. Configuration Resources resources: - name: micro-app type: git source: uri: https://github.com/bendodd/micro-app.git
9. Configuration Tasks jobs: - name: say-hello-world plan: - get: micro-app trigger: true - task: say-hello-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./pass.sh
10. - name: say-goodbye-world plan: - get: micro-app trigger: true passed: [say-hello-world] - task: say-goodbye-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./fail.sh jobs: - name: say-hello-world plan: - get: micro-app trigger: true - task: say-hello-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./pass.sh
11. - name: say-goodbye-world plan: - get: micro-app trigger: true passed: [say-hello-world] - task: say-goodbye-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./fail.sh jobs: - name: say-hello-world plan: - get: micro-app trigger: true - task: say-hello-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./pass.sh
12. - name: say-goodbye-world plan: - get: micro-app trigger: true passed: [say-hello-world] - task: say-goodbye-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./fail.sh jobs: - name: say-hello-world plan: - get: micro-app trigger: true - task: say-hello-world config: inputs: [name: micro-app] platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: dir: micro-app path: ./pass.sh
13. UI
14. UI
15. UI
16. UI
17. UI
18. UI
19. $ fly set-pipeline Echo Before I was lost! Echo Now I’m found! Apply configuration: [yN] :
20. $ fly execute $ fly -t my-cci execute \ --config tests.yml --input code=.
21. $ fly hijack $ fly -t my-cci hijack \ --job some-pipeline/some-job
23. Examples Super Mega Awesome
24. Getting Started Learning by Example
25. HELP!
26. After ▪ Configurable as code ▪ Unpolluted builds ▪ Scaleable ▪ Fast feedback ▪ Learnt in a single-sitting ▪ Platforms & Software
27. Give it a go? @bendodd @armakuniHQ http://concourse.ci/getting-started.html