CasC

[samuelbernardolip]

Improve current SQAaaS deployment for Jenkins and JePL to follow a continuous configuration architecture.

CasC (configuration as code, also known as CAC) improves the approach of IAC (infrastructure as code) since it brings up a level in the management representation. So while IAC can be seen as the implementation do manage the infrastructure, with CasC the representation goes forward including all environments configurations backed by VCS (in our case git).

To accomplish this, all code from Jenkins side will be deployed using Kubernetes platform instead of current VM IAC based deployment. Using Jenkins Operator with Jenkins job DSL plugin, we can achieve a complete reproduced environment for any instance of Jenkins, following GitOPS CD implementation, focusing on a developer-centric experience.

References

https://www.cloudbees.com/blog/configuration-as-code-everything-need-know/
https://dzone.com/articles/infrastructure-versus-config-as-code
https://dzone.com/refcardz/continuous-configuration-essentials?chapter=1
https://www.cloudbees.com/blog/infrastructure-as-code/