Exploring Jenkins X Environments
This lesson discusses Jenkins X environments and their types in detail.
We’ll continue using the go-demo-6 application. This time, we’ll dive deeper into the role of the staging environment and how it relates to the process executed when we push a change to an application.
Let’s take a look at the environments we currently have.
jx get env
The output is as follows.
NAME LABEL KIND PROMOTE NAMESPACE ORDER CLUSTER SOURCE REF PRdev Development Development Never jx 0staging Staging Permanent Auto jx-staging 100 https://github.com/vfarcic/environment-jx-rocks-staging.gitproduction Production Permanent Manual jx-production 200 https://github.com/vfarcic/environment-jx-rocks-production.git
NAME column
We already experienced the usage of the staging environment, while the other two might be new.
dev environment
The dev environment is where Jenkins X and all the other applications that are involved in continuous delivery are running. That’s also where agent Pods are created and live during the duration of builds. Even if we were not aware of it, we already used that environment or, to be more precise, the applications running there.
production environment
The production environment is still unused, and it will remain like that for a while longer. That’s where we’ll deploy our production releases. ...