...
Add Salesforce Org to the Opsera portal
click Click on Tool Registry (found at the left panel of options as shown below)
...
2. Click on ‘New Tool’ (as shown below) - To add SFDC Org to establish an initiation.
...
3. Enter tool details as explained below,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
...
4. Click Create
...
6. 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)
...
...
7. Click Save. This will save the tool Configuration The tool configurations will be updated successfully and Salesforce org has been successfully added to Opsera portal.
...
Next - Create Source Code repository for your pipeline (Gitlab/githubGithub/bitbucketBitbucket)
8. Click on Tool Registry on left navigation panel and click on ‘New Tool’.
...
9. Enter the following values:
Tool Name
...
Tool Identifier
...
- Select the
...
Source Code Management (SCM) tool from the
...
dropdown
Description
...
10. Click Create button to save.
...
12. Click on Navigate to the Tool → Click on ‘Connection’ tab → Enter the following values:
URL
...
Username
...
Personal Access Token
...
...
13. Click ‘Save’ → Tool Configuration Save to update the tool’s configurations will be updated successfully. This would successfully add the repository SCM tool to the Opsera portal. After saving the tool, ensure the Connection is successful but by clicking ‘Test Connection’Connection
Next, Add Jenkins tool to be added, and integrated with source code repository integrate with Source Code Management
14. Click on Tool Registry on left navigation panel and click on ‘+New Tool’.
...
15. Enter In Create New Tool form, enter the following values:
Tool Name
...
Tool Identifier
...
- Select Jenkins from the drop down
...
.
Description
...
16. Click Create
...
17. Click on the Tool → Click on ‘Connections’ tab → Enter Jenkins URL, UserID, and navigate to 'Connections’ tab. Enter the following values:
Jenkins URL
Jenkins Port
Jenkins User ID
Jenkins Token
...
18. Save tool and then click ‘Test Configuration’ to ensure connection succeeds.→ succeeds→ Tool Configuration configurations will be updated successfully.
...
19. Click on Accounts tab
...
20. Click on ‘Register ‘+ Register New Account Credentials’ button
...
21. Create New Jenkins Account adding form will open
...
23. Select Platform [Select your source code repository management tool from the drop down - Gitlab/Github/Bitbucket], Then drop down for “tools” will be enabled - Select the tool that you just created.
...
Platform - Select your Source code management platform from the dropdown. Choose from Gitlab, Github and Bitbucket.
Tool - Select the recently created tool from the dropdown.
24. Enter Name and Description of credentials to be added in Jenkins and click on ‘Save’ button. The Jenkins job Job is now linked to your source code repository.
...
...
SFDC Jenkins
...
Jobs creation in
...
(each one represents the SFDC Process such as Validate Package XML, Backup of an Org, Unit Test, Deploy to an Org)
...
Tools
Each job represents an SFDC Process:
SFDC Jenkins Jobs:
SFDC Create XML Package
Profile Migration
SFDC Validate XML Package
SFDC Backup
SFDC Deploy
SFDC Unit Test
SFDC Push Artifacts
25. In the Opsera portal - Navigate to Tool Registry and select the Jenkins tool you just created. Navigate to the Jobs tab and click on ‘+ Create Job’ Job button (as shown below)
...
26. Select Job Type as ‘SFDC Jobs’ and Build Step as ‘SFDC Validate XML Package’. Make the following selections:
Job Type - SFDC Jobs
Build Step - SFDC Validate XML Package
Enter a Name and Description.
...
27. Click ‘Save Job’ Create button to finish creating the job.
...
28. Job The job has now been created on in the Jenkins Tool which will be used on in Pipelines to successfully create builds inside Jenkins.
29. Repeat the above job process for creating other jobs for --> SFDC Backup, SFDC Unit Test and SFDC Deploy
...
Jobs have been created and configured and all ready for use. This is a one time configuration activity & can be used repeatedly for “n” number of pipelines.
...
Pipeline Creation
...
and
...
Configuration
30. On the Opsera portal , Click on navigate to Pipelines from the left navigation panel to open the catalog to create pipeline. Click on ‘Catalog’ Tab (found at the right top panel as shown below)
...
31. From the below list of pipeline templates, Under the ‘Salesforce Template’, click on “ Create Pipeline “ to add the pipeline successfullyIn the Marketplace in Pipeline Templates, locate Salesforce Template, and click + Create Pipeline to create a pipeline using this template.
...
32. To give a meaningful name for rename the pipeline, On navigate to Summary tab , and click on the pencil icon (next to SalesForce Template name). Next to the pipeline template name - “SalesForce Template”.
...
33. Edit the pipeline by editing any additional details. Click the Save icon to save the new name.
...
Create Package XML job & Configuration
34. Click on Navigate to Workflow tab → .
A default step ‘Create ‘SFDC Jenkins Create Package Job’ will be available
...
35. Click on the ‘Configuration icon’ gear icon on the ‘Create SFDC Jenkins Create Package Job’ step → It will open the fields for adding the configurationJob step to view the Step Configuration form.
...
36. Enter the below fields and click Save
Tool → - From the dropdown, select the Jenkins tool created in Tool Registry;
Job Type → - The default Job Type for Package creation job is ‘SFDC Package generation job’, for Generation Job’. For other steps, it should be is ‘Opsera managed jobs’.
SalesForce Salesforce Credentials → - Source Org from which modified files will be fetched
Account → [gitlab/github/bitbucket] credentials added inside Jenkins tool in tool registry - Select the source control management credentials that were added in the Tool Registry. Choose from Gitlab, Github or Bitbucket.
Workspace/Project → Based upon the Account - All Projects will be fetched [Select one]Repository → Based upon the Project Select the Workspace or Project in the the source control management account.
Repository - All the repositories available will be fetched [Select one]from the selected Workspace.
37. Click Save → all the configurations made to the step will be saved.
...
SFDC process includes , ‘Create Package XML’, ‘Validate XML’, ‘Backup’, ‘Unit Test’ and ‘Deploy’ the following steps in pipeline, where each one the pipeline:
Create Package XML
Validate XML
Backup
Unit Test
Deploy
Each can be used based upon the organization need and each can be plugged in/out based upon necessity.
...
Add a Validate XML
...
pipeline step to the workflow
38. Click on ‘Edit workflow’ option on the pipeline as shown below.
...
39. Click on ‘+' icon present below the ‘Jenkins SFDC Jenkins Create Package Job’ → It will add a Job.
A new step called 'Unconfigured step’ will be added to the workflow.
...
40. Click on ‘Done Editing’ and Done Editing then click on ‘Pencil’ the pencil icon on ‘Unconfigured Step’ →
Step detail fields Setup will be openedopen.
...
41. Enter a ‘Step name’ and select the tool as ‘Jenkins’values for the fields:
Step Name - Enter a unique step name.
Tool - Select Jenkins. Note: Tool cannot be changed after form is saved. To change the tool, delete the step and create a new one.
Tags - Select any tags to be applied at this level.
...
42. Click Save button to save the step level details.
...
43. Click the gear icon (⚙️)→ Configuration fields will open
...
66. Pipeline Start Wizard will be opened → where components of modified files need to be selected.
...
On the wizard, you have the option to select/deselect modified files, view/edit the package XML and use a past run’s XML .
...
Manual Pipeline Wizard Run
...
Use Past Run’s XML and XML/File Upload Process
...
Choose from Source Org:
If From Git is selected, you may include dependencies. By default, all CustomObject dependencies are included in the deployment while selecting components from the Git Side. By disabling this toggle, dependencies will be excluded from Git to SFDC merge unless explicitly selected. This can also be selected in a manual pipeline run on the following Component Type selection screen:
...
If dependencies are included in the pipeline run, verify their details in the Console log after the pipeline has run from Git to SFDC:
...
XML/File Upload Process
...
67. Select the date & components and click on ‘Proceed with Selected Components’
...