Jenkins

We’ve prepared a Jenkins for you so you can easily run and monitor different stages of the CI-CD. You can access the Jenkins by visiting [your-company-name].btq.sealights.co and enter the username (a

Overview of the Jenkins

Once you log in you will be able to see We’ve already put some jobs in there. We’ll explain them to you one by one.

Jenkins jobs

Overview of the jobs

• hello: This one just echos hello world, just to make sure that the Jenkins is working.

• BTQ-CI: This is the main pipeline, it’s a multi-branch pipeline for the repository you have been provided. You will be able to see one branch which is ‘public'. Running that job will clone the 'public’ branch in the repository using the Jenkinsfile in it and will go through all the CI-CD pipeline of building the images and running the tests on them.

• BTQ-BUILD: Goes to the dockerfile of a specified microservice, builds the container and pushes it to an ecr we’ve provided.

• update-btq: Since we’re running both Jenkins and the boutique on one machine we don’t actually lunch another instance for running tests. We only update the Kubernetes using helm upgrade.

• test_runner: Runs the tests in the repository with an image we’ve prepared.

• BTQ-nodejs-tests-Cypress-framework: Is the job for running cypress tests. (We put it in a seperate job because we’re running the tests in a container. If you use cypress you know why if not don’t bother).

Every job is explained further in the job’s description, for all jobs pipelines (except update-btq) you can go to the repository jenkins->jenkinsfiles->[job name].

For more information about the Jenkins configuration and images go here.

To access the Jenkins cluster you have to ssh to the ec2 (DNS and key are provided), then write export KUBECONFIG=$(k3d kubeconfig write jenkins). then any kubectl operation like kubectl get pods will be on the Jenkins.

For how we configured the yaml pods:

Pods configuration

For details on the jobs and and running them:

Running the jobs and seeing the results