Why We Moved Our CI/CD Stack

Do you recognize the urge to keep improving certain processes? In this story, you will read the reasons for changing your CI/CD strategy from a developers perspective.

Koen van Zeijl
Geek Culture

--

Photo by Iva Rajović on Unsplash

Introduction

One of the areas that Nalta — The company that I work for — is involved in, is helping customers with their digital transformation. But a few years ago, Nalta also started her own transformation, just like she does for her customers. As a company that works together with innovative companies, it is important to continue innovating yourself. At the end of 2016, it became known more techniques became possible in the world of automation. Tools were launched to automate building and deploying software.

How we started

In the early years of software development, we used to develop according to the waterfall method. During this time we only released the software once every 3–4 months. As more experience has been gained, the Waterfall method has not always proved to be the right method. During the development process, customers often come forward with adjustments and additions. This is why Nalta decided to work with iterative development methods. Working with smaller iterations also meant we had to release the software…

--

--

Koen van Zeijl
Geek Culture

I help you keep up to date with C#, Azure DevOps and all sorts of nice to know tools | You can buy me a beer at https://ko-fi.com/koenvanzeijl