How Cloud Foundry is CI'd
SpringOne Platform 2016 Speaker: Amit Gupta; Product Manager, Pivotal. Find out how Cloud Foundry does continuous integration, from a GitHub pull request against a small repository to an official final release. See how we're striving to raise the bar for open source projects when it comes to rigor, automation, and transparency of our CI. We’ll talk about how we: -integrate work from community contributors and core Foundation contributors, spread across multiple teams and continents; -test at multiple layers, from fast, tightly-scoped unit tests, to full blown deployments and acceptance tests across multiple IaaSes; and -keep the full end-to-end process transparent to the community; not just the source code, but also the build pipelines and the discussions that surround artifact promotion. The audience will come away with strategies for continuously integrating and deploying their own Cloud Foundry installations or other distributed systems.
Recommended
More Related Content
What's hot
What's hot(20)
Viewers also liked
Viewers also liked(7)
Similar to How Cloud Foundry is CI'd
Similar to How Cloud Foundry is CI'd(20)
More from VMware Tanzu
More from VMware Tanzu(20)
Recently uploaded
Recently uploaded(20)
How Cloud Foundry is CI'd
- 1. CI and CD for CF By Amit Kumar Gupta @amitkgupta84
- 2. CI 2
- 3. CD(eliverability) 3
- 4. CF 4
- 5. Goal 5 ship CF with SPEED and CONFIDENCE
- 6. Confidence is a Human Problem 6
- 7. Good CI is Necessary 7 Automated Comprehensive Comprehensible Tests Reproducible Reusable Stateless CI Pipelines
- 8. … but not Sufficient 8 Pairing Small StoriesPM Acceptance Product+Eng Collaboration
- 9. Unique Challenges 9 PaaS-as-a-Product Pivotal Elastic Runtime Pivotal Web Services Distributed System Distributed Team
- 10. CF CI: Overview 10
- 11. Key Tool: BOSH 11 “COMPILER” CONSISTENC Y DECLARATIVE for distributed systems between environments configuration
- 12. Key Tool: Concourse CI 12 BOSH INTUITIVE DECLARATIVE deployed read-only web UI configuration
- 13. Key Tool: CATS 13 COMPREHENSIV E COMPREHENSIBL E SHARED feature coverage BDD framework among dev teams
- 14. CF CI: Component Pipeline 14
- 15. CF CI: Integration Pipeline 15
- 16. Example: CVE + Major Regression 16 48:00 Pivotal Web Services Pivotal Web Services
- 17. Example: Delete CI 17
Editor's Notes
- • So that we can: ◦ reduce chance of doing something wrong ◦ reduce the risk when something is done wrong ◦ make it easy to do things right ◦ make it easy to ask questions and understand why our CI is right
- • Distributed System: ◦ complex setup and config ◦ no one understands all pieces • Distributed Team: ◦ 40+ teams, 7+ timezones, 8+ companies ◦ ~15% contributed by non-Pivotal
- Each pipeline progresses from fast-feedback unit tests to slower, full-deploy-and-acceptance-tests, before promoting
- • Pull components • Deploy, smoke-test, and acceptance-test in multiple configurations • Promote release candidate • manual approval by many PMs • cut final release