Search⌘ K
AI Features
Home
Courses
The DevOps Toolkit: Working with Jenkins X

Verifying Jenkins X Boot Installation

Explore the process of verifying a Jenkins X Boot installation within a Kubernetes cluster by examining active pipelines and the lazy creation of namespaces. Understand how GitOps principles manage environments including dev, staging, and production, and learn to trigger and monitor pipelines through code changes to ensure proper setup.

We'll cover the following...

Checking the pipelines #

Let’s take a quick look at the pipelines currently active in our cluster.

Shell
jx get pipelines --output yaml

The output is as follows:

C++
- vfarcic/environment-jx-boot-dev/master
- vfarcic/environment-jx-boot-production/master
- vfarcic/environment-jx-boot-staging/master

We are already used to working with production and staging pipelines. What is new is the dev pipeline. That is the one we just executed locally. It is now available in the cluster as well, and we should be able to trigger it by pushing a change to the associated repository. Let’s test that.

Triggering the dev pipeline #

We’ll explore the Jenkins X upgrade process later. For now, we just want to see whether the dev repository is indeed triggering pipeline activities. We’ll do that by making a trivial change to the README.md file.

Shell
echo "A trivial change" \
    | tee -a README.md
git add .
git commit -m "A trivial change"
git push
jx get activities \
    --filter environment-$CLUSTER_NAME-dev \
    --watch

We pushed the changes to GitHub and started watching the activities of the dev pipeline. The output, when the activity is finished, should be as follows.

D
STEP                                      STARTED AGO DURATION STATUS
vfarcic/environment-jx-boot-dev/master #1       4m10s    3m52s Succeeded 
  release                                       4m10s    3m52s Succeeded 
    Credential Initializer 7jh9t                4m10s       0s Succeeded 
    Working Dir Initializer Tr2wz               4m10s       2s Succeeded 
    Place Tools                                  4m8s       2s Succeeded 
    Git Source Vfarcic Environment Jx...         4m6s      36s Succeeded https://github.com/vfarcic/environment-jx-boot-dev.git
    Git Merge                                   3m30s       1s Succeeded 
    Validate Git                                3m29s       1s Succeeded 
    Verify Preinstall                           3m28s      26s Succeeded 
    Install Jx Crds                              3m2s      10s Succeeded 
    Install Velero                              2m52s      12s Succeeded 
    Install Velero Backups                      2m40s       2s Succeeded 
    Install Nginx Controller                    2m38s      16s Succeeded 
    Create Install Values                       2m22s       0s Succeeded 
    Install External Dns                        2m22s      16s Succeeded 
    Install Cert Manager Crds                    2m6s       0s Succeeded 
    Install Cert Manager                         2m6s      16s Succeeded 
    Install Acme Issuer And Certificate         1m50s       2s Succeeded 
    Install Vault                               1m48s       8s Succeeded 
    Create Helm Values                          1m40s       3s Succeeded 
    Install Jenkins X                           1m37s     1m3s Succeeded 
    Verify Jenkins X Environment                  34s       5s Succeeded 
    Install Repositories                          29s       5s Succeeded 
    Install Pipelines                             24s       1s Succeeded 
    Update Webhooks                               23s       4s Succeeded 
    Verify Installation                           19s       1s Succeeded

That’s the first activity (#1) of the dev pipeline. To be more precise, it is the second one (the first was executed locally) but, from the perspective of Jenkins X inside the cluster, which did not exist at the time, that is the first activity. Those are the steps of Jenkins X Boot running inside our cluster.

We won’t go through the changes that were created ...