Running Your First Pipeline
Last updated
Last updated
Getting started with your first pipeline.
This tutorial will help you with running your first pipeline with ozone. Let’s start …
Pre-requisites required before running a pipeline Attach a cluster : Create a Provider: Create a microservice: Ok great, Now you are one step closer to running a pipeline…
Check for the Catalog under the CI/CD section. Then click on Task Templates. Now we will see lots of templates. We have covered almost all the use cases from cloning a repository, to scanning for vulnerabilities, to building an image, to deployments. Hmm .. sounds great ..But, what if I want to create my task for my own use case? Well, we have covered that as well. Click on + Task Template on the top right you will be navigated to Ozone Studio.
Initially, we sample a template for printing “hello world” once you get to know the syntax and what params are necessary for a valid task template. you can customize your own task and add you steps as shown below(clone a repo)
You can search this template with its display name. In the above picture, the display name is “hello world”. so in templates, you can search directly by Hello World in the task templates section. Great, you have successfully created a task. yet we are closer to another step Now check the Pipeline Templates, As I told you we have covered almost all use cases in tasks so as in pipeline templates. but still, we can create our own pipeline, and let's run that pipeline.
Click on + New pipeline on the top right you will get 2 options one is create manually and another is create using auto-generate, select manually, and continue.
Now you will be redirected to Ozone Studio.
If we have a look on top then 4 things need to be addressed, Pipeline name: The name of the pipeline. Rollback Pipeline: Pipeline rollbacks are a crucial aspect of any continuous integration/continuous deployment (CI/CD) process, allowing teams to revert to a previous version of their application or infrastructure in case of errors or issues detected after a deployment. so, you select any pipelines from the dropdown and use it as a rollback in case of failure. Description: you can give your own description ( for ex: This pipeline can clone the repo and scan for vulnerabilities using trivy scan). Tags: Tags are an important part of filtering out pipelines when we deal with tons of pipelines. After filling in all these, Now we can see there is a button called +Add Tasks, if we click on that we can see there are tasks that we have created in the previous step as well as well as the featured tasks that are offered by ozone.
Just click on + Add Task it will get added to the pipeline as shown below.
