With Opsera, you can automate any stack, build pipelines for any app, and deploy anywhere. Opsera accelerates best-practice CI/CD adoption so software teams can deliver software faster, safer, and smarter!Opsera allows users to build their own pipeline 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. You specify what you require to be accomplished and Opsera will handle the 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 a Pipeline from Catalog
...
Select a “Blank Pipeline template” by clicking “view”Locate a pipeline template and click ‘Create Pipeline’ button.
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 Configure your pipeline with stages that you want including steps (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 Provide the required fields to configure your SCM (Gitlab, Github or bitbucketBitbucket) as shown in the below image.
Provide the a step name
Choose the platform (gitlab, or github or bitbucket)
Select an account
choose the repository from your SCM repo
Platform type. The following SCM platforms will be available for selection: Gitlab, Github or Bitbucket.
Select an Account. The dropdown will include configured tools from the Tool Registry specific to the selected Platform.
Choose the Repository from your configured SCM tools
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 configured Jenkins server tool 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 Job Type, configured in your jenkins
...
Jenkins tool’s Jobs tab.
