Running the jobs and seeing the results

As you know (unless you skipped it) we've prepare a Jenkins for you with jobs that we think you'll be interested in and will build/have something similar in your CI-CD.

Here we're going only to explain what are these jobs, what they do and what you should expect. More details on how the jobs does the task can be found in the jobs' description.

Introduction

We've made the Jenkins for 3 main reasons:

• Giving an example of how the CI-CD should look like when adding Sealights to your environment.

• Being able to rerun the same job how many times you want and see the changes live.

• Giving a playground for you to experiment with different things to have a better grasp on how Sealights works and help you plan how to integrate it to your CI-CD and try many different things, for example what if you build using one token and deploy using another (Spoiler: doesn't matter because it's only for authentication).

The CI-CD pipeline

The CI-CD pipeline follows a very simple template, BUILD->Deploy on testing environment-> run tests

Pipeline overview

BTQ-CI: Running the entire CI-CD