Salesforce Quick Deployment Documentation

Opsera now adds support for Quick Deployment feature, which can be used to deploy an already successfully validated and tested component package against the same Salesforce Org. As part of execution a unique Deployment Job ID is generated which can be used and quick deploy can be performed.

Prerequisite: In order to trigger the Salesforce Quick Deploy Task, you must first trigger a SFDX/ANT pipeline with a unit test case to generate the Salesforce Deploy Key. See Fetching Deploy Key section for instructions.

1 Salesforce Quick Deploy Task Configuration
2 Fetching Deploy Key
3 Troubleshooting Failed Quick Deployments

Salesforce Quick Deploy Task Configuration

Navigate to Tasks menu and click Create New Task.

2. In Create New Task form, enter a name and choose “Salesforce Quick Deploy” as Type

3. Select the Org and enter the Deploy Key and click create <Deploy Key Fetch is explained below>

4. Once created - Click “Run Task” and run

5. In Opsera Task Confirmation, click Validate Deploy Key to view the list of components & Unit test details.

6. Click Run Task to Proceed.

6. Successful deployment log can be viewed in Task Activity Logs.

Fetching Deploy Key

Trigger a SFDX/ANT pipeline with Unit test case.

2. Deploy ID is generated and can be fetched from Pipeline Logs by clicking on Report row. In Summary tab - Overview, copy the field provided for Request ID:

Troubleshooting Failed Quick Deployments

Failure Message	Description

Failure Message	Description
`ERROR running force:source:deploy: INVALID_ID_FIELD: There have been deploys in the org since the source validate happened`	This suggests that the provided Validation deployment Job ID is no more applicable for Quick Deploy because of following reasons : A recent regular deployment / quick deployment execution has happened post the Validation. The provided deployment job ID was created as part of validation that happened 10 days prior.
`ERROR running force:source:deploy: INVALID_ID_FIELD: Source validate did not run tests in the org`	This suggests that the provided Validation deployment Job ID didn’t include any Unit test level or was having NoTestRun selected as part of the execution and therefore not eligible for Quick Deployment.
`ERROR running force:source:deploy: INVALID_ID_FIELD: Source validate does not meet the cutoff criteria for testless deploy`	This suggests that the provided validation deployment Job ID does not meet either of the below criteria's : ID provided for the validation job is unsuccessful/in-progress. ID provided for the validation job is not having test execution available. ID provided for the validation job is not having test coverage criteria (75%) met.
`ERROR running force:source:deploy: INVALID_ID_FIELD: Source is not a check-only deploy`	This suggests that the provided Validation deployment Job ID is not a job ID created as part of Validation but rather as part of Deployment and therefore is not applicable for Quick Deployment.
`ERROR running force:source:deploy: UNKNOWN_EXCEPTION: invalid parameter value`	This suggests that the provided Validation deployment Job ID is not a valid Salesforce deployment ID and therefore not applicable for Quick Deployment.
`ERROR running force:source:deploy: UNKNOWN_EXCEPTION: unexpected metadata`	This suggests that the provided Validation deployment Job ID is not a valid Salesforce deployment ID and therefore not eligible for Quick Deployment. This can also occur if the Job ID was created as part of Apex Test Run (Unit Testing) step.