Jenkins X Workshop
Welcome to The Jenkins X Files - the Jenkins X workshop. Or yet-another-jenkins-x-workshop.
Why this workshop?
Because we wanted a simple-enough set of applications that people can play with, and that represent more or less (part of) our stack:
- a React frontend UI -> Scully
- a Go backend API -> Mulder
- a database - here we are using Redis because it's easy to setup and use, but any database would do
The goal of this workshop is to write the CI/CD pipelines for the whole stack, connecting applications together.
Initial Setup
Before starting, you'll need to create a new Jenkins X cluster. This is well documented in the Jenkins X Documentation.
For example, on GKE we used the following command:
$ jx create cluster gke -n jx-workshop -p MY_GCP_PROJECT -z europe-west1-b -m n1-standard-2 --min-num-nodes 3 --max-num-nodes 5 --default-admin-password=PLEASE_CHANGE_ME --default-environment-prefix jx-workshop
and then just used the default options everywhere.
Note that if you have an error while creating the new cluster, you can add the --verbose flag to get more details - usually a permission issue if you are using a public cloud provider.
Let's get to work!
Now that everything is ready, you need to make a choice: Mulder or Scully? But don't worry, it can also be both!
You need at least to start somewhere. If you plan to do both, you should start with Mulder: implement the CI/CD pipeline for the backend API first, and then deploy the frontend UI on top of it. That way, you will be able to re-use your Mulder Helm chart when deploying Scully.
- Start here for the Mulder Workshop
- Or here for the Scully Workshop
And if you had time to finish everything, you can do the Integration Workshop.