Continuous Deployment with Docker and Openshift
•Download as PPTX, PDF•
1 like•579 views
Continuous deployment with Docker and Openshift allows for: 1) Creating a pipeline for DevOps that starts with a new branch, keeps the scope small, and has a viable test suite. 2) Protecting the master branch by requiring checks of branch status and deploying with Docker after tests pass on a CI server. 3) Strategies for continuous deployment including git pushing to trigger CI testing and building Docker images for deployment to Openshift or other environments.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (12)
Recently uploaded
Recently uploaded (20)
Continuous Deployment with Docker and Openshift
- 1. CONTINUOUS DEPLOYMENT With Docker and Openshift
- 2. PHILIPPE LAFOUCRIÈRE • @plafoucriere • philippe@gemnasium.ca • http://philippe.lafoucriere.com
- 4. CONTI ? Continuous Integration Continuous Delivery Continuous Deployment
- 6. PIPELINE FOR DEVOPS Always start with a new branch Keep the scope small Viable Test Suite
- 7. Protect master branch Requirements Check branch status
- 10. ATLASSIAN, NEW!
- 11. DOCKER
- 12. STRATEGIES git push CI Test & Build CI docker push Docker deploy git push CI Test & Hook Openshift Build Docker push
- 13. SHOWTIME!
- 14. QUESTIONS
Editor's Notes
- [JP]
- L'intégration continue est un ensemble de pratiques utilisées en génie logiciel consistant à vérifier à chaque modification de code source que le résultat des modifications ne produit pas de régression dans l'application développée. Le principal but de cette pratique est de détecter les problèmes d'intégration au plus tôt lors du développement, et d’améliorer la qualité du code et du produit final. CI: Branch and Merge often CD: means that the team ensures every change can be deployed to production but may choose not to do it, usually due to business reasons. In order to do continuous deployment one must be doing continuous delivery. CDep: Push to production every change
- Source: Wikipedia Do this on a regular basis, even if no change in your code.
- Prerequisites to start CD
- Elect team leaders, responsible for the master branch Define requirements, in terms of code coverage, code lint, tests, dependencies, etc. Check branch automatically, and prevent merge if broken
- Example with gitlab
- Announced today
- case 1 : all the work is done on the CI server. Openshift is just a distant registry. Registry MUST be exposed (route) case 2 : all the work is done in Openshift. A new Image is created, and pushed to the internal registry.
- Openshift is an opensource PaaS edited by RedHat. We will be using the version 3, rewritten in Go, and featuring Docker and Kubernetes