...
24. Enter Name and Description of credentials to be added in Jenkins and click ‘Save’ button. The Jenkins Job is now linked to your source code repository.
...
SFDC Jenkins Jobs creation in Tools
...
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
...