How Jenkins 2 works and how to automate it, presented on the meetup SET (Software Exploratory Test) in Stockholm, Magine's office.

1. Modern Jenkins
How Jenkins 2 works and how to automate it
by Camilo Ribeiro

2. Agenda
• Quick intro to Magine
• Camilo who???
• Intro to Jenkins evolution at Magine
• What benefits we see on the current platform
• Demo!!!
• Questions and discussion
But feel free to interrupt and ask for questions
or clarifications at any time

3. Magine
magine.com

4. Camilo
@camiloribeiro
camilo@camiloribeiro.com
• Brazilian, Software Engineer and Fika enthusiast
• Started breaking systems in 2005
• Today tries to keep them from breaking in first place
• Worked as tester, developer and Infra/Ops
• Uses Jenkins since Hudson times
• Automation freak
• Before Magine, worked at ThoughtWorks and Klarna

5. How it was before

6. How it was before
• Copy from previous job
• Needed jenkins person on the team
• Usually needed Infra/Ops support
• Kept old habits and bad design from job to job
• Not automated at all

7. How it got better

8. How it got better
• All automated with delivery-pipeline plugin
• Tons of groovy code (we found out it to be a problem)
• No need for jenkins “specialist” on team, but highly
dependent on infra/ops
• Hard to customize while reusing (just as complex as
coding)
• Several more jobs created (one job/step)
• Drive-model off devops mentality

9. How the pipeline is now

10. How the pipeline is now
1. Single file is added to any repository/branch on
the organisation
2. A new pipeline line is created on that brach
3. Works :)

11. Benefits of the pipeline now
• Highly flexible
• Super easy to reuse in a Team Level
• Credentials can be used without knowing them
• Enforces ownership of pipelines by the teams
• No dependency on Infra/Ops for anything*
• Fully automated

12. How Jenkins is now

13. How the Jenkins is now
• Both Master and Agentes are created by Ansible Scripts and
provisioned with packer on AWS
• They have all needed libs and docker installed
• Master starts the day with zero instances and uses autoscaling
groups to increase capacity depending on demand
• On idle the agentes are turned off to save money
• Jenkins / Github organisation integration provides easy access to
code and integration with PR and events
• AMI Access to Master and Agents
• Use some NFSs to keep caches shared on agents (ex: sbt cache)

14. Demo
github.com/camiloribeiro/cdeasy

15. Keywords
• Ansible
• HashiCorp Packer
• Amazon EC2 / Cloudformation (or GCP, Azure, etc)
• Groovy
• Docker
• Git

16. Learn / Practice
https://github.com/camiloribeiro/cdeasy

17. We are hiring!!!
http://app.jobvite.com/m?3VR9Diwl

18. Tack!