Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Salesforce offers quick deploy where any pipeline with validate step with unit test are eligible. As part of exaction a unique ID is generated which can be used and quick deploy can be performed.

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.

In this section:

  • Fetch Deploy Key

  • Create and Run Salesforce Quick Deploy

  • Troubleshooting Failed Quick Deployments

Fetch Deploy Key

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. Trigger a SFDX/ANT pipeline with Unit test case. 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:

Create and Run Salesforce Quick Deploy Task

  1. Navigate to Tasks menu and click Create New Task.

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


Troubleshooting Failed Quick Deployments

Here are a few common failure messages that you’d encounter and the reasons for the failures.

  1. 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 :

    1. A recent regular deployment / quick deployment execution has happened post the Validation.

    2. The provided deployment job ID was created as part of validation that happened 10 days prior.

  2. 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.

  3. 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%).

  4. 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.

  5. 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.

  6. 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.

  • No labels