Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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 with the tools and cloud of your choice.

  1. Create Pipeline from Catalog

  2. Select a “Blank Pipeline template” by clicking “view”

  3. 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 (smile) 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).

  1. 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.

    1. Provide the step name

    2. Choose the platform (gitlab, or github or bitbucket)

    3. Select an account

    4. 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.

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.

  1. Choose the Jenkins server that you want to use it for your pipeline

  2. Provide port if it is different from 8080

  3. Provide Jenkins User ID

  4. Provide the Jenkins job name as is in your jenkins

Note: Please update your tool registry with your account and authentication information so that the above details shown in the image gets populated.
  • No labels