There are a lot of Continuous Integration services but Jenkins is still one of the most used in most programming languages. In this talk I will share the CurrencyFair experience, how our IT Team made of 40 engineers manage CurrencyFair delivery with GitHub, Jenkins, Hubot and Slack on different environments. Artifact to guarantee the stability of your codebase, pipeline and some Jenkins’s plugins in order to create the most comfortable delivery flow for your projects.
15. 1. Unique pipeline
There are a lot of rules but all projects and all teams are different, study and build
the best pipeline for your project and your team.
16. 2. face the front but don't forget the past
The new code is awesome but your pipeline must
work also during a disaster
17. 3. Speedy
in 1 minutes I can maintain the focus on the execution but 15 minutes are a lot,
you can take a coffé or start to think about another task.
Return back to your old task requires some effort.
20. 6. Track! Track! Track!
Monitor the productivity and mark your important steps
21.
22.
23. 7. Communication layer
Create the best communication flow between your
continuous integration system and your team, your
goal is disable the Jenkins UI
Only for strong hearts
29. Your CI server is
the unique door
to production.
● monitor
● logs
● recovery
● HA
● scalability
●
30. Jenkins supports Master/Slave scalability.
You can distribute builds across different nodes.
https://jenkins.io/doc/book/architecting-for-scale/
31. Backup/Restore policy
What will we do during a disaster? Are we able to recover?
I backup JENKINS_HOME excluded plugins.
There are plugins to backup if you need.
38. Thanks a lot
Site Reliability Engineer at InfluxData.
Open source maintainer and Docker Captain
@gianarb
https://gianarb.it
http://scaledocker.com
see you here! 6.15pm to speak about Docker security!