Continuous Integration & Continuous Deployment

Transcript

1. C [ I | D ] Indra Gunawan Continuous Integration & Continuous Deployment
2. Indra Gunawan Ø Senior Web Developer at OttenCoffee.co.id Ø Creator PaketHub.com Ø Email: indragunawan@outlook.com indra@kongkow.club @IndraGunawan
3. Agenda Ø What Ø Why Ø CI Tools Ø Travis-CI Ø Demo
4. Continuous Integration is a software development practice where members of a team integrate their work frequently … verified by an automated build (including test) to detect integration errors as quickly as possible. - Martin Fowler
5. Why Continuous Integration Ø Run your tests in the real world. Ø Increase your code coverage Ø Deploy your code to production Ø Build stuff faster Ø Don't break stuff Ø Decrease code review time
7. Continuous Integration Tools Ø Travis CI (https://travis-ci.org/) Ø CircleCI (https://circleci.com) Ø GitLab CI (https://about.gitlab.com/features/gitlab-ci- cd) Ø TeamCity (https://www.jetbrains.com/teamcity) Ø Jenkins (https://jenkins.io) Ø and many more…
9. Fire CI Process $ git push
12. Continuous Deployment software development practice in which every code change goes through the entire pipeline and is put into production automatically, resulting in many production deployments every day. It does everything that Continuous Delivery does, but the process is fully automated, there's no human intervention at all. - Marcia Ramos
14. Travis CI
15. Travis CI – Single Build
16. Travis CI – Env Vars
17. Travis CI x GitHub
18. Basic CI Configuration Ø Machine and Language specific Ø Branch selection Ø Command or Scripts Ø Notifications
19. .travis.yml
20. Continuous Deployment
22. DEMO
23. Question and Answer ?