We want to deliver software faster and faster, Continuous Delivery is everywhere - let's learn what to look after when modeling a delivery pipeline and how to implement one as a code!
We want to deliver software quickly and in a stable way, thus approaches like Continuous Delivery become more and more popular. A crucial part in this plays the delivery pipeline – the process that describes how we build, release and test our application.
Nowadays, almost all parts of the systems we build are defined as code, including the underlying infrastructure and its configuration. The same can be done for our delivery pipelines – we can describe what happens from the moment the developers push their work to the repository, to making it available for our users on production. This way, we end up with a direct and concrete implementation of our process, which in return, like a regular software, can be tested – an activity testers are familiar with.
During the workshop, we will take an example application and design and implement all stages of its delivery pipeline using open source tools like Docker, Jenkins and Jenkins Pipelines… and real pipes! We will:
- learn how we build the application
- run the required tests
- release a new version of the application
- deploy the application on a ‘production’ environment
The exercises will help you understand the whole process of delivery from a more technical point of view and in the end give you more insight in the way you do the same within your project/team.
Basic knowledge about Docker will help, although all the necessary information will be provided during the workshop.