CI Pipelines and SemVer
Command CI Pipelines with help of Semantic Versioning
Semantic Versioning (also referred to as SemVer) is a standard versioning system that has been followed by software engineers and developers for a while now. This is introduced to maintain the dependency graph intact with the applications.
By keeping the dependency graph intact, the application can remain stable. To do so semantic versioning standards are defined with a 3-component number in the format of X.Y.Z, where
As of today, this semantic versioning standard is followed widely almost in all languages and artifacts. Starting from the node.JS npm package to the Kubernetes release versions.
In this cycle, during the CI/CD pipelines, it is becoming very crucial to make some decisions based on the semantic versions within the CI Pipelines that are running. For example, let’s dive into a simple scenario with helm charts. The helm charts are packaged as tgz
files. Of course, now the helm packages are OCI complaints. That doesn’t change anything relating to the process and naming convention of the charts. These ‘tgz’ files are suffixed with the version of the chart. Meaning…