Innovate and Collaborate- Harnessing the Power of Open Source Software.pdf
IBM Bluemix Continuous Delivery
1. Continuous Delivery
with IBM Bluemix
bluemix.net/devops
Niklas Heidloff, IBM
Developer Advocate
@nheidloff
July 2017
2. AgendaAgenda
• Concepts and Terminology
• Demo: Simplest Pipeline
• Demo: Microservices application and Delivery Insights
• Demo: Third party tools
• Discussion
@nheidloff
3. Why is Continuous Delivery important ?Goals
• Get user feedback as quickly as possible
• React quickly to new requirements and provide fixes
• Reduce deployment risks by deploying smaller pieces
@nheidloff
4. Continuous DeliveryTerminology
• Ability to deliver new functionality constantly and rapidly
• Deployment pipelines are used to automate ...
– Creating builds
– Running various tests
– Deploying to different environments
@nheidloff
5. Continuous DeploymentTerminology
• Deployments to production environments
– Versus deployment possibilities in Continuous Delivery
• Something is done when it is deployed and used by people
– Opposite from “It works on my machine”
• Allows getting user feedback
– For MVPs as well as for continuous improvements
– Via A/B testing
@nheidloff
6. Continuous IntegrationTerminology
• New code is tested frequently in the master branch
– To detect issues early and locate them easily
– To prevent the traditional “integration hell”
• Requires automation on various levels
• Everything needs to go under source control, including
configuration
@nheidloff
7. DevOpsTerminology
• Collaboration between developers, operations professionals
and other IT professionals
• DevOps enables organizational
environments to collaborate, from
product design over deployments
to learning from users
• Required for continuous delivery
@nheidloff