Servers, containers, and serverless deployment-as-code

The main pipeline that currently being used, at least in part, was in Jenkins. Although Jenkins is not considered a GitOps tool, the ability to leverage the core GitOps practices through it is possible. Through the use of Jenkins Pipelines, the team could design the execution engine in Jenkins and allow users to maintain a single declarative configuration file, known as a Jenkinsfile. This Jenkinsfile would live in each Git repository, meaning that the integration process and deployment process configurations could be defined and stored per team. And, since the DevOps team was already familiar with Jenkins, they wanted to evaluate Jenkins as a potential purist GitOps tool.

Initially, the GitOps setup in Jenkins required the ability to build any type of artifact. Natively, Jenkins can build the artifacts for their legacy environment fairly well. But, for containerized artifacts, the team would have to either build that process...