Continuous Integration and Automation on Jenkins

Automate all the things!

Transcript

1. Continuous Integration and Automation on Jenkins Akhyar Amarullah <akhyar@onebitmedia.com> Onebit Engineering Brownbag Session Friday, 28 February 2016
2. Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Martin Fowler
3. Why Continuous Integration Rapid Feedback Reduced Risk Collective Ownership Continuous Deployment Offload from people
4. Jenkins is an open- source continuous integration server
5. Popular Hosted Jenkins Alternatives Travis CI Shippable Drone.io etc
6. But why Jenkins? Flexibility
7. Basic Jenkins functionalities Notice a change Check out source code Execute builds/tests Record and publish results Notify developers
8. Jenkins Terminologies - Job - Workspace - Environment - Source VCS - Build Step - Post-Build Step - Artifact - Nodes - Master - Slave - Plugins
9. Sample CI pipeline
10. Continuous Integration Best Practices Single Source Repository Commit often Make Your Build Self-Testing Automate the Build Build fast
11. Automated Testing Best Practices Start from clean state Isolate as much as possible
12. Jenkins Best Practice Separate master and slave nodes Label slave nodes based on available features Automate slave provisioning (e.g. Ansible, Docker) Notify developers on failed build (e.g. email, slack) Docker reduces app environment setup headaches a lot
13. Future Plan
14. Automate code style review and approval Automate service deployment Automate APK/IPA deliveries to tester/end-users Automate scaling Automate the Jenkins itself Future Plan