...
37. Click Save → all the configurations made to the step will be saved.
...
As a token of verification, a ‘SFDC_Create Package XML'’ build job will be created in Jenkins which will have ‘Pipeline and Step ID’ suffix for unique identification.
...
SFDC process includes, ‘Create Package XML’, ‘Validate XML’, ‘Backup’, ‘Unit Test’ and ‘Deploy’ steps in pipeline, where each one can be used based upon the organization need and each can be plugged in/out based upon necessity.
...
51. Configuration section will be closed and the given details will be saved
...
52. As a token of verification, a ‘SFDC_Backup’ build job will be created in Jenkins which will have ‘Pipeline and Step ID’ suffix for unique identification.
...
Next Pipeline Step Configuration for Unit Test
(All the test classes will be executed for this step)
5352. Similar to above steps - New step for Unit test can be added
...
5453. Click on ‘Pencil icon’ on Unconfigured step and add Step level details
...
5554. Click on Save to save the step details
...
5655. Click ‘Configuration icon’ → configuration fields will open
...
5756. Enter Tool, Job Type, Job, Salesforce Credentials field values and Click on 'Create Job and Save button’
...
5857. Configuration section will be closed and the given details will be saved
...
59. As a token of verification, a ‘SFDC_Unit Testing’ job will be created in Jenkins which will have ‘Pipeline and Step ID’ suffix for unique identification.
...
Next Pipeline Step Configuration for “ Deploy”
(Destination SFDC Org to be configured where the modified files created as part of ‘Create Package XML’ step will be deployed )
6058. Similar to above steps - New step for Deploy can be added
...
6159. Click on ‘Pencil icon’ on Unconfigured step and add Step level details
...
6260. Click on Save to save the step details
...
6361. Click ‘Configuration icon’ → configuration fields will open
...
6462. Enter Tool, Job Type, Job, Salesforce Credentials field values and Click on 'Create Job and Save button’
...
6563. Configuration section will be closed and the given details will be saved
...
66. As a token of verification, a ‘SFDC_Deploy’ job will be created in Jenkins which will have ‘Pipeline and Step ID’ suffix for unique identification.
...
The necessary steps of SFDC Process has been configured successfully. Now the pipeline can be started / initiated to run.
...
67. Custom Object ‘SFGA__Ad_Group_ID__c’ is taken as an example here [image taken before deployment in SFDC]
...
6864. On Git, Same custom object File ‘SFGA__Ad_Group_ID__c’ is modified for ‘Inline help text’ field and committed.
...
6965. In the Opsera Portal → Navigate to the configured pipeline → Click on ‘Start Pipeline’. as shown below.
...
7066. Pipeline start wizard will be opened → where components of modified files need to be selected.
On the wizard, we have the option to select/deselect modified files and view/edit the package xml.
...
7167. Select the date & components and click on ‘Next’
...
7268. Modified files for selected components will be displayed from both Git/Bitbucket as well as SFDC.
Select the respective files & click on “Proceed with selected SFDC files” - Either Select the components from the list or upload components as a csv file to use for deployment.
...
7369. This will open the necessary steps to be executed. In this example, “ Unit testing “ - Click on the “unit testing “ box to open up the the testing classes. This needs to be specified . Please select each step below and then apply the required testing classes before proceeding. Please note, without this step, the pipeline cannot complete successfully. Once the necessary files are selected → Click on Next → To view the package XML
...
** Easier and simpler UI framework for enhancing Unit Test class selection.
** Bulk addition of Apex Test Classes can be made by multi-selecting the test classes displayed on the left-side table and clicking on Add Selected Button on top of the corresponding table.
** Bulk removal of selected Apex Test Classes can be made by multi-selecting the test classes displayed on the right-side table and clicking on Remove Selected Button on top of the corresponding table.
...
7470. Modified files will be converted to package XML for deployment → Click on Proceed to start the Opsera pipeline
...
7571. Opsera Pipeline process started as shown below
...
7672. Create Package Job is successful as shown below. Once Create Package job is successful, next pipeline step will be automatically taken for processing.
...
7773. Validate XML step is successful → which indicates modified files and its related objects are available in Package XML.
...
7874. Backup step is successful → This indicates a ‘Rollback branch’ created in Git repository tool and all the SFDC Components are backed up.
...
7975. Output of Backup Step - Git branch created.
...
8076. All the components and files of Source SFDC Org mentioned in Pipeline Backup step is backed up here.
...
8177. Unit test step is successful → which indicates all the test classes are successfully executed in respective SFDC Org mentioned in Pipeline step.
...
8278. Deploy step is successful → which indicates the modified files from Git are successfully deployed to Salesforce Destination Org as mentioned in pipeline step.
...
8379. Salesforce Destination Org has been updated with modified content from modified file in Git
...