Webinar: How Workday Improved their Security Posture with Opsera | Register Now

Overview

No items found.

Installation

Source Code repository (Gitlab/Github/Bitbucket)
Steps to configure Salesforce pipeline in Opsera

Opsera Admin

No items found.

User Guides

No items found.

Lorem Ipsum

No items found.

Create Source Code repository for your pipeline (Gitlab/GitHub/Bitbucket)

  • Click on Tool Registry on left navigation panel and click on ‘New Tool’
  1. Enter the following values:
  • Tool Name
  • Tool Identifier - Select the Source Code Management (SCM) tool from the dropdown
  • Description

‍

Steps to configure Salesforce pipeline in Opsera

  1. Login into the Opsera Portal (https://portal.opsera.io/) and sign in with your registered email

Add Salesforce Org to the Opsera portal

  1. Click on Tool Registry (found at the left panel of options as shown below)
  1. Click on ‘New Tool’ (as shown below) - To add SFDC Org to establish an initiation
  1. Enter Tool Details in Create New Tool form:
  • Tool Name - Give a meaningful name for the tool
  • Tool Identifier- Select ‘SFDC Configurator’ from the drop down
  • Description - Give a description for the tool
  1. Click Create
  1. Once the tool is created, Click on ‘Connection’ tab to enter the details.

Enter values for the following fields:

  • Domain URL - Salesforce URL
  • SFDC Username
  • SFDC Client ID
  • SFDC Client Secret
  • SFDC Token
  • Password
  • Build Type - Ant Migration or Salesforce DX (SFDX)
  1. Click Save. The tool configurations will be updated successfully and Salesforce org has been successfully added to Opsera portal.

Salesforce Pipelines User Guide

Opsera offers no code DevOps orchestration platform, making it easy for developers to maintain the code/tools and enabling faster releases. Opsera's enterprise customers accelerate their Salesforce deployments by nearly 50% to 75%

Integrating DevOps in Salesforce can be a daunting process with complicated release challenges:

  1. Multiple release cycles and on-demand change
  2. Complexity in business needs and salesforce ecosystem (CPQ, Apptus, etc)
  3. Lack of security and compliance
  4. Varied point solutions for different applications

Opsera is an end-to-end solution that takes care of the entire software development lifecycle, including choosing the right tools, deploying automated configurations, merging components, version control, continuous deployments, and automated regression testing. It allows users to orchestrate Salesforce DevOps tools across their development ecosystem seamlessly, eliminating the bottlenecks of traditional development tools. The development team gets the flexibility to automate entire pipelines with their favorite CI/CD tools, access a large pool of integrations, gain end-to-end visibility, real-time governance, and data backups.

Getting Started

These topics provide basic information and instructions for first-time users of Opsera Salesforce Pipelines

Before You Begin

Prerequisites and requirements for creating Opsera Pipelines once your account has been provisioned

  • Salesforce credentials, Salesforce org URL, client ID, secret key, token, and password
  • Credentials of Source code Repository such as Gitlab/GitHub/Bitbucket

Logging into Opsera

Login into the Opsera Portal (https://portal.opsera.io/) and sign in with your registered email.

Configure tools in Opsera Tool Registry

  • Salesforce Org
  • Configure
  • Source Code repository (Gitlab/GitHub/Bitbucket)
  • Configure
  • Jenkins
  • Prerequisite for Jenkins < Get from prereq >
  • Configure Jenkins
  • Configure jobs in Jenkins
  • Each job represents an SFDC Process. Please follow these steps to configure each process which will be required in the pipeline
  • SFDC Create XML Package < Details>
  • Profile Migration < Details>
  • SFDC Validate XML Package < Details>
  • SFDC Backup < Details>
  • SFDC Deploy < Details>
  • SFDC Unit Test < Details>
  • SFDC Push Artifacts < Details>

Create Salesforce Pipeline

  • SFDC process includes the following steps in the pipeline and these stages can vary as per your organization's needs.
  • Create Package XML <Details>
  • Validate XML <Details>
  • Backup <Details>
  • Unit Test <Details>
  • Deploy <Details>

Sample pipeline run

  • Here is what successful pipeline execution looks like. This pipeline is successfully deploying to SFDC org from the git repository.

‍