Opsera pipelines follow a declarative model. This means that you focus on what steps are required throughout the pipeline and now how those steps are accomplished. This approach can be accomplished using both the Opsera UI or a pipeline JSON configuration file. Regardless, you specify what you require to be accomplished and Opsera will handle how it is handledthe rest.
This tutorial will walk you through how to create and configure the steps within an Opera Pipeline with the tools and cloud of your choice.
...
Create Pipeline from Catalog
Select a “Blank Pipeline template” by clicking “view”
Update the fields marked in * for accurate logging and analytics purpose.
...
4.Click “workflow” next to the summary tab to view the pipeline workflow as shown in the below image.
...
If you are here , then Congratulations 
You are only few steps away from building a robust declarative pipeline.
Now let's see about configuring your pipeline with stages that you want including (connecting to your SCM, Build, Unit testing, Static code analysis, Functional testing, Artifact upload, Docker push, Container scan and deployment).
Source code Repository:
On the right side of the screen please provide the required fields to configure your SCM (Gitlab, Github or bitbucket) as shown in the below image.
Provide the step name
Choose the platform (gitlab, or github or bitbucket)
Select an account
choose the repository from your SCM repo
Note: Please update your tool registry with your account and authentication information so that the above details shown in the image gets populated.
As part of Opsera data privacy and security, any token or authentication information is encrypted and stored in Vault and Opsera or anyone within Opsera will not have any control or visibility to your token or passwords.
2.Configuring Build:
On the right side of the screen please provide the required fields to configure your Build (Jenkins or Teamcity) as shown in the below image.
Choose the Jenkins server that you want to use it for your pipeline
Provide port if it is different from 8080
Provide Jenkins User ID
Provide the Jenkins job name as is in your jenkins
...