Continuous Everything v2.0
0 likes•149 views
This document discusses continuous integration and continuous delivery practices. It defines continuous integration as integrating work frequently, usually daily, and verifying integrated changes through automated builds and tests. The key principles of continuous integration include maintaining a single source repository, automating builds and self-testing, committing to the mainline daily, and immediately fixing broken builds. Continuous inspection uses tools like SonarQube to detect issues like code duplication. Continuous delivery builds on continuous integration by automating the deployment process to allow for frequent, reliable releases.
Continuous Everything v2.0
- 1. Continuous Everything Soumyak Bhattacharyya Product Developer DevOps Enthusiast
- 3. Simple ideas are easier to understand. Ideas that are easier to understand are repeated. Ideas that are repeated change the world.
- 5. 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. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Principles 1. Maintain a Single Source Repository 2. Make Your Build Automated & Self-Testing 3. Everyone Commits To the Mainline Every Day 4. Every Commit Should Build the Mainline on an Integration Machine 5. Fix Broken Builds Immediately 6. Keep Build Fast 7. Test Environment Is A Clone Of Production Environment 8. Binary Lives In Binary Repository 9. Radiate Information 10. Automate Deployment Reference : https://martinfowler.com/articles/continuousIntegration.html Cost Risk Bugs Quality Speed Visibility Outcome Continuous Integration
- 6. CI Server Binary RepositoryStatic Analyzer Deployment Environment Version Control System VM VM Conceptual Flow Check - In Pull Inspect Build – Run Unit Test Push Deploy Developers Continuous Integration
- 7. Jenkins ArtifactorySONAR TomcatGitHub VM VM Typical Implementation Check - In Check Out Inspect Build – Run Unit Test Push Deploy Developers Pull Continuous Integration
- 8. Job Configuration Slave Plugin Build Test Inspect Deploy Cloud Pipeline Administration Notification Jenkins Continuous Integration
- 9. 6000 + Downloads per month 1500 + Subscriber to mailing list 60 + Open Source Plugin 150,000 + Downloads • Code Duplication • Bad Distribution of Complexity • Spaghetti Design • Lack of Unit Test • Insufficient Coding Standard • Potential Bugs • Inadequate Comment … and so on https://www.sonarsource.com/ Continuous Inspection
- 10. 1. Integrate with CI Engines, Build Tools (Maven / Gradle) 2. Host and proxy 1. Maven Dependencies 2. Docker Images 3. NuGet packages 4. node.js packages 5. Bower registry 6. PyPI distributions 7. Microsoft .NET ecosystem 3. Watch / Filter / Search for artifacts Deploy 1. To facilitate artifact storage & proxy 2. To avoid hitting public remote repository 3. To avoid being inefficient, unreliable and non – secure 4. To deploy, manage and share local artifacts 5. To establish full control on artifact resolution 6. To build once and deploy many times RepositoryManager Continuous Integration (Produce binary) Features
- 11. Demo Time
- 13. Why Do We Need Continuous Delivery Cycle Time : Act phase of OODA loop Cycle Time is the reaction time of Organization OODA loop By John Boyd Continuous Delivery
- 14. Continuous Delivery (vs. Deployment)
- 15. Continuous Delivery Conceptual Flow Continuous Integration Continuous Delivery Continuous Deployment
- 16. Demo Time
- 17. Big Picture
- 19. Q & A