We previously saw the benefits of representing configuration as code, primarily infrastructure as code files. The same motivations led to pipeline as code definitions, configuration that specifies the CI server pipeline steps.
In the past, many CI servers such as Jenkins required to be configured manually. CI server jobs had to be laboriously clicked together to build up pipelines. Especially, rebuilding pipelines for new applications or feature branches thereof required cumbersome manual work.
Pipeline as code definitions specify the Continuous Delivery pipeline as part of the software project. The CI server builds up and executes the pipeline appropriately, following the script. This vastly simplifies defining and reusing ...
