Retrieve Jenkins X Activities, Logs, Pipelines, and More
This lesson explores how we can retrieve information concerning Jenkins X through the command line and the initial GitHub release created by Jenkins X.
While UIs are nice to look at, I am a firm believer that nothing beats the command line concerning speed and repeatability. Fortunately, we can retrieve almost any information related to Jenkins X through jx executable.
Retrieving activities
We can, for example, get the last activities (builds) of those jobs.
The output is as follows:
We can see that there were activities with each of the three jobs. We had one deployment to the production environment (environment-jx-rocks-production), and two deployments to staging (environment-jx-rocks-staging). The first build (activity) is always performed when a job is created. Initially, environments only contain a few applications necessary for their correct operation. The reason for the second build of the staging environment lies in the creation of the jx-go project. One of the steps in its pipeline is in charge of promoting a successful build to the staging environment automatically. When we explore jenkins-x.yml in more detail, you’ll get a better understanding of the process, including promotions.
The last activity is of the jx-go pipeline. So far, we did not push any change to the repository, so we have only one build that was run when the job itself was generated through the quickstart process.
Applying filters on activities
Listing the ...