Beginning with concourse
Download as PPTX, PDF1 like453 views
The document introduces Concourse CI, highlighting its focus on continuous delivery pipelines, where each step is designed to establish trust and is executed through various tools. It emphasizes a pipeline-first approach, container-based solutions, and the importance of defining processes as code using three core abstractions: task, job, and resource. The conclusion underscores the significance of understanding failure in engineering for successful implementation.
Beginning with concourse
- 1. Beginning with concourse.ci Miel Donkers Hylke Stapersma 12-04-2017
- 2. Beginning with concourse.ci Introduction • Introduction • Chain of trust • Chain of tooling • Problems • Concourse constellation • Concourse concepts • Demo 2
- 6. Beginning with concourse.ci 6 Hylke Stapersma Software craftsman @hylke1982 Miel Donkers Software craftsman @mieldonkers
- 8. Beginning with concourse.ci 8 Every step in a continuous delivery pipeline adds trust
- 11. Beginning with concourse.ci 11 Every step is an execution of tools
- 13. Problems 13
- 14. Beginning with concourse.ci 14 Pipeline as first class citizen
- 15. Beginning with concourse.ci 15 Configuration cannot be rebuild from code
- 16. Beginning with concourse.ci 16 Tooling dependencies
- 17. Concourse.CI 17
- 18. Beginning with concourse.ci 18 Pipeline first
- 19. Beginning with concourse.ci 19 Container based
- 20. Beginning with concourse.ci 20 Configuration as code
- 27. Beginning with concourse.ci 27 Baggage claim
- 32. Demo time 32
- 34. Conclusion 34
- 35. Beginning with concourse.ci Conclusion • Concourse is pipeline oriented • Workers are tools agnostic (container centric solution) • Process is defined as code • Concourse only has 3 simple abstractions (task, job, resource) 35
- 36. 36 “Successful engineering is all about understanding how things break or fail.” Henry Petroski
Editor's Notes
- #6: Intro codecentric 20 man NL 350 man DE Near-shoring +1 Tijd
- #7: Introduction Miel/Hylke
- #9: Every step increases trust in the application Almost every step is automated
- #10: Every step increases trust in the application Almost every step is automated
- #12: Collection of tools for: Building Testing Security Deployment
- #13: Collection of tools for: Building Testing Security Deployment
- #15: Tools like Jenkins are Job centric Jobs are failing pipeline might not
- #16: CD process is bound by the project Rebuilding by hand is tedious and error prone Jenkins has pipeline-dsl/job-dsl Regenerate process with a single action
- #17: CD Process is dependent on tools Tools have versions Tools must be installed on build servers Tools can conflict within a shared build environment
- #19: Pipeline is a first class citizen in Concourse.ci
- #20: Build steps are isolated in containers No configuration is allowed to enter Concourse server
- #21: The process can only be configured as code
- #23: Airport orientated names UI / Scheduler Laten zien
- #24: Airport orientated names UI / Scheduler Laten zien
- #25: SSH Server Worker / Server communications
- #26: Controller for containers (Linux, Mac, Windows)
- #27: CLI tooling for conctrolling CI
- #28: Distributed Volumes Handy for maven repo etc…
- #30: Execution in a (custom) container Execution of a script Uses a resources Can be set of jobs
- #31: Abstraction for GETTING and PUTTING stuff
- #32: Single Unit Comparable with a state machine
- #34: Collection of actions Plan