Continuous Delivery pour vos applications avec Cloud Foundry et Jenkins
1. Continuous Delivery pour vos
applications Cloud Natives avec Jenkins
et Cloud Foundry
Erwan Bornier – Cloud Platform Architect, Pivotal
16 Février 2016
Now, you might have seen some version of the story where several Silicon Valley companies are disrupting traditional industries and creating tremendous value.
Uber has no cars, AirBnB owns no real estate, Facebook doesn’t generate content and Amazon has no retail stores. This is all based on software. And that’s really a great story
At Pivotal, we really see these trends as manifestations and facets of the same thing – that we call CLOUD NATIVE.
CLOUD NATIVE is the coming together of tools, frameworks and building modern software on a cloud infrastructure
At Pivotal, we really see these trends as manifestations and facets of the same thing – that we call CLOUD NATIVE.
CLOUD NATIVE is the coming together of tools, frameworks and building modern software on a cloud infrastructure
At Pivotal, we really see these trends as manifestations and facets of the same thing – that we call CLOUD NATIVE.
CLOUD NATIVE is the coming together of tools, frameworks and building modern software on a cloud infrastructure
At Pivotal, we really see these trends as manifestations and facets of the same thing – that we call CLOUD NATIVE.
CLOUD NATIVE is the coming together of tools, frameworks and building modern software on a cloud infrastructure
What is Continuos Delivery?
CD is basically a mechanism desirable by any business - how to shorten the length of time from coming up with a profitable idea to actual delivery of that idea (to make profit).
When applied to software, and delivery of new product to market, typically their are many stages involved in delivery of this idea, many things which need to be accomplished along that line.
To reduce this line you have to 1) Eliminate the steps that don’t add any value and 2) Automate as many steps as possible, by making the first task on any software effort “delivery” - deploy the code somewhere, even if it doesn’t do anything.
This allows developers to focus on being innovative and not to be drawn into lengthy processes, hand-offs between silo’d teams etc.
Once you have this in place, keep doing that every time you change anything…
L’Objectif recherché depuis tjrs: : design, develop, test, deploy le tout rapidement to put the service in front of f the customer ,
En s’inscrivant dans une chaine vertuesue de rapprochement et de collaboration entre le dev et les operations ( la prod)
to success/fail fast
et get rapidly feedback to enhance the features
Presenter: Cyrille - speaker: Bjorn
Presenter: Cyrille - speaker: Bjorn
Presenter: Cyrille - speaker: Cyrille
externalize all of that environemnt sepcific config
CF really provides great ways to do this