BTQ-CI: Running the entire CI-CD

When going to BTQ-CI you will see the two branches, public and changed-branch, (DO NOT run changed-branch it will not work because it's not meant to). By clicking on "public"

then "BUILD WITH PARAMETERS" you will be able to run the entire pipeline.

The BTQ-CI has different stages, we'll give you a brief introduction to each one of them.

Build BTQ: Building the microservices

When running the BTQ-CI job it will first run BUILD-BTQ 10 time, one per microservice since each BUILD-BTQ job builds a container for a microservice. You will be able to see that when running kubectl get pods.

As you can see above the the BTQ-CI lunches 10 pods, 9 now because of resource limit yet after a while it will lunch the 10th

It will build all the microservices and uploads them to the ecr.

For more info one the BUILD-BTQ go to the page below and the job description in Jenkins

update-btq: Deploys the microservices to the test environment

After building the containers and pushing them to the ecr and it will be the time to deploy them in order to run tests on them.

Deploying the microservice is done via the update-btq job, from it's name it doesn't deploy a new machine or cluster, it replaces the existing pods with the new ones.

Test runner: Runs the tests

Time to test your apps, as you should know we've prepared examples for all testing frameworks that we support, for the list go here. For what to expect when running the pipeline