CI/CD (DevOps) 101
3 likes1,727 views
Talk about the basic principles and concepts of CI/CD as a set of practices in order to reduce integration errors through automated implementations for testing and deployments as well as the tooling behind this philosophy.
Ad
More Related Content
What's hot (20)
Similar to CI/CD (DevOps) 101 (20)
Ad
More from Hazzim Anaya (6)
Ad
Recently uploaded (20)
![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
CI/CD (DevOps) 101
- 3. CONTINUOUS INTEGRATION • Continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day.
- 4. CONTINUOUS INTEGRATION • Git • Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. • Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.
- 5. CONTINUOUS INTEGRATION • Git (front ends) • Gitlab • Github • Bitbucket
- 6. CONTINUOUS INTEGRATION • Then... we have code and branches, now what?
- 7. CONTINUOUS INTEGRATION • let's build, but… what it's a build?
- 8. CONTINUOUS INTEGRATION • In the field of software development, the term build is similar to that of any other field.That is, the construction of something that has an observable and tangible result.
- 9. CONTINUOUS INTEGRATION • Build automation is the process of automating the creation of a software build and the associated processes including: compiling computer source code into binary code, packaging binary code, and running automated tests.
- 10. CONTINUOUS INTEGRATION • Maven • Gradle • Ant • Make
- 11. CONTINUOUS INTEGRATION • ok, we did a Build and now what????
- 12. CONTINUOUS INTEGRATION • Now we have an Artifact!!!… But WTH!? is an artifact?
- 13. CONTINUOUS INTEGRATION • Artifacts can be used to represent data created as a side-effect of running a build. Artifacts are files which are associated with a single build.A build can have any number of artifacts associated with it.
- 14. CONTINUOUS INTEGRATION • Artifactory • Nexus • Archiva
- 15. CONTINUOUS INTEGRATION • But who controls and manage all of this stuff? it’s magic? DevOps people are wizards?
- 16. CONTINUOUS INTEGRATION • Here is were we use a continuous integration software that supports our continuous integration process, in which developer's changes are immediately tested and reported when they are added to the mainline code base.
- 17. CONTINUOUS INTEGRATION • Jenkins • TeamCity • TravisCI
- 18. CONTINUOUS INTEGRATION • Our orchestrator did the build and deploy the artifact, now what?
- 19. CONTINUOUS INTEGRATION • We can't have CI without automated testing.
- 20. CONTINUOUS INTEGRATION • Junit • Selenium • Robot • Test with custom scripts
- 21. CONTINUOUS INTEGRATION • But where is all this automated testing executed?
- 22. CONTINUOUS INTEGRATION • Another part of CI/CD and DevOps is "Infrastructure as code", the capability of create and destroy servers under demand for specific needs or testing, with the fiability everytime will we have the same config.
- 23. CONTINUOUS INTEGRATION • For local environments: • Vagrant • Docker compose*
- 24. CONTINUOUS INTEGRATION • Public/private/Hybrid clouds: • Terraform • AWS Cloud formation.
- 25. CONTINUOUS INTEGRATION • Where are that servers hosted?
- 26. CONTINUOUS INTEGRATION • Google Cloud Platform (GCP) • Amazon Web Services (AWS) • OpenStack • Rackspace *VM’s and Containers.
- 27. CONTINUOUS INTEGRATION • How can I manage the configuration to be the same always and across all my environments?
- 28. CONTINUOUS INTEGRATION • Ansible • Puppet • Chef
- 29. CONTINUOUS INTEGRATION • How can we know the health of my environments and get alerts in time?
- 30. CONTINUOUS INTEGRATION • Zabbix • PagerDuty • Graphite • Prometheus
- 31. CONTINUOUS INTEGRATION • And log management?
- 32. CONTINUOUS INTEGRATION • Splunk • Papertrail • ELK - (Elasticsearch, Logstash, and Kibana)
- 33. CONTINUOUS DELIVERY • Continuous delivery is an extension of continuous integration to make sure that you can release new changes to your customers quickly in a sustainable way. • This means that on top of having automated your testing, you also have automated your release process and you can deploy your application at any point of time by clicking on a button.
- 34. CONTINUOUS DELIVERY • In theory, with continuous delivery, you can decide to release daily, weekly, fortnightly, or whatever suits your business requirements. However, if you truly want to get the benefits of continuous delivery, you should deploy to production as early as possible to make sure that you release small batches, that are easy to troubleshoot in case of a problem.
- 35. CI/CD & DEVOPS
- 36. DEVOPS • DevOps is a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). The main characteristic of the DevOps movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and infrastructure management.
- 37. DEVOPS
- 38. RELATED ROLES
- 39. DEVSECOPS • DevSecOps strives to automate core security tasks by embedding security controls and processes into the DevOps workflow. DevSecOps originally focused primarily on automating code security and testing, but now it also encompasses more operations-centric controls.
- 40. NETDEVOPS • NetDevOps is a culture, movement, or practice that emphasizes the collaboration and communication of both network architects and operators while automating the process of network design and changes. It aims at establishing a culture and environment where building, testing, and releasing network changes can happen rapidly, frequently, and more reliably.
- 41. SRE • Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies that to IT operations problems.The main goals are to create ultra- scalableand highly reliable software systems.
- 42. DEVOPS • "DevOps is never a straight line. It's a forest,And like a forest it's easy to lose your way...To get lost...To forget where you came in. -Hattori Hanzo - Kill Bill
- 44. CONTACT • [email protected] • [email protected] • @HazzimIO