Seminarie: Ordina

In a world where everything evolves at the speed of light, in a world where the fast fish eats the slow fish, in this world applications need to evolve fast. This means releasing new features, bug fixes for incidents and improvements often, preferably multiple times a day.

As the saying goes, anything worth doing twice is worth automating. Hence, automating the entire build, test, and rollout process is crucial for making quick and seamless changes, pushing updates into production within hours or days. Esteemed companies such as GitHub, Zalando, and Netflix have demonstrated the viability of this approach, consistently updating and deploying software on a daily, even hourly, basis. The caveat is maintaining a high level of confidence that these changes won't disrupt the application.

During this talk, Pieter Vincken will discuss the history of making changes to software, how automation has made it possible to make changes often and how in recent years the same methodology is used for supporting infrastructure through Infrastructure As Code. The talk will discuss a typical CI/CD setup and how changes flow from the head of the business analyst through the developers into the hands of the end-user using the application. Spoiler, automation is key and with speed emerging as a byproduct of robust testing practices, rather than the primary goal.

Topics:

• What is Continuous Integration (CI)?
• What is Continuous Deployment/Delivery (CD)
• Typical CI/CD setup explained.
• CI/CD examples for Java using Docker and Kubernetes
• What is versioning? (Conventional commits, semantic versioning, and releasing)
• Artifact promotion
• Hands-on lab creating a pipeline