Quick Deployment for Salesforce enables you to quickly deploy code to productiondeploy a pre-validated successful package. This is ideal for instances in which your organization has multiple test methods, resulting in a longer release time. You require To use this Quick Deploy option, you must have a successfully validated and tested component package against the same Salesforce Org in order to use the Quick Deploy option.
Workflow
Salesforce account and deploy key are required to run the Quick Deploy workflow. The workflow comprises creating a Quick Deploy task under Tasks section. Previously, you had to start an SFDX/ANT pipeline in Opsera to retrieve the deploy key. When the account and deploy key are entered after the task has been created, the task is prepared to be executed.
...
Login to Opsera and navigate to Products > Pipeline.
Open and trigger a SFDX/ANT pipeline with a unit test case.
Once the pipeline is triggered, navigate Salesforce pipeline that includes an executed Validate step.
Navigate to Pipeline Logs and click Report under the Log Type column.
Under Summary tab, click Overview.
Copy the displayed Request ID.
The fetched deploy key is required to run the Salesforce Quick Deploy task.
...
Name: Enter a name for the task
Type: Select the type as Salesforce Quick Deploy from the dropdown.
Salesforce Account: Select the Org.
Salesforce Deploy Key: Enter the deploy key that was retrieved from the triggered SFDX/ANT Salesforce pipeline.
3. Click Create.
4. In Opsera Task Confirmation popup, click Validate Deploy Key to view the list of components Components Details & Unit test details Test Details.
...
5. Click Run Task.
Once the task is successfully executed, you can view the deployment log under Activity Logs.
...
Troubleshooting Failed Quick Deployments
In the process of Salesforce Quick Deploy, a few failures may occur. The Console Log available as part of the Task Activity Logs will display these failures in the form of error messages.
Here are a few common failure error messages that you would encounter and , along with the reasons for the failures to help you troubleshoot.
ERROR running force:source:deploy: INVALID_ID_FIELD: There have been deploys in the org since the source validate happened
This occurs when the the provided Validation deployment Job ID is no more applicable for Quick Deploy. This can be due to the 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 error occurs when the provided Validation deployment Job ID was executed with NoTestRun chosen or without any Unit test levels. Therefore it becomes ineligible for Quick Deployment.ERROR running force:source:deploy: INVALID_ID_FIELD: Source validate does not meet the cutoff criteria for testless deploy
This error occurs when the provided validation deployment Job ID does not meet any of the below criteria:
(i) ID is unsuccessful or in-progress.
(ii) ID is not having test execution available.
(iii) ID doesn’t meet the test coverage criteria (75%).ERROR running force:source:deploy: INVALID_ID_FIELD: Source is not a check-only deploy
This error occurs when 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
The error occurs when 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 Test) Step.
...