Versioning Releases Through Tags

Getting all running applications #

Before we start “playing” with versions, we’ll take a look at what we’re currently running in the staging environment.

In my case, go-demo-6 version 0.0.211 is running in the staging environment. Your version is likely going to be different, and if you did not destroy the cluster at the end of the previous chapter, you are probably going to see that a release is running in production as well.

🔍 If you forked go-demo-6 after I wrote this chapter (April 2019), your version is likely going to be 1.x.x or 2.x.x. That’s OK. It does not matter which version you’re running right now.

Before we see how we can control versions through Jenkins X pipelines, we’ll take a quick look at the jx-release-version CLI. It is already used inside our pipelines, and understanding how it works will help us get a better grip at how we can combine it with our processes.

There are two ways we can proceed with the examples that involve jx-release-version.

1. You can visit the