In a world where rebuilding your software development process from scratch is just as important as rebuilding your software, there is the need for a tool that can facilitate automation of the Continuous Delivery pipeline. The new kid on the block Concourse.ci can take care of that. This presentation will help to get a better understanding on the basic principles of Concourse.ci, give a better understanding what the difference is between Concourse.ci and Jenkins and implementation tips and tricks will be shared.
The first part of the presentation will consist of sharing the basic concepts of Concourse.ci and how they relate to each other; tasks, jobs and resources, which form the main building blocks.Jenkins is another popular CI/CD tool, but the concepts of Concourse.ci and Jenkins differ. In the second part of the presentation a comparison of the basic concepts of both tools will be given. This can help to select the right tool for the problem at hand.During the demo part of the presentation the basic concepts will be shown and an simple continuous delivery pipeline will be build.
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
Intro codecentric
20 man NL
350 man DE
Near-shoring
+1 Tijd
Introduction Miel/Hylke
Every step increases trust in the application
Almost every step is automated
Every step increases trust in the application
Almost every step is automated
Collection of tools for:
Building
Testing
Security
Deployment
Collection of tools for:
Building
Testing
Security
Deployment
Tools like Jenkins are Job centric
Jobs are failing pipeline might not
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
CD Process is dependent on tools
Tools have versions
Tools must be installed on build servers
Tools can conflict within a shared build environment
Pipeline is a first class citizen in Concourse.ci
Build steps are isolated in containers
No configuration is allowed to enter Concourse server
The process can only be configured as code
Airport orientated names
UI / Scheduler
Laten zien
Airport orientated names
UI / Scheduler
Laten zien
SSH Server
Worker / Server communications
Controller for containers (Linux, Mac, Windows)
CLI tooling for conctrolling CI
Distributed Volumes
Handy for maven repo etc…
Execution in a (custom) container
Execution of a script
Uses a resources
Can be set of jobs