Versions Compared

Old Version 7

changes.mady.by.user Christina

Saved on

compared with

New Version Current

changes.mady.by.user Rajeswar Rajendran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Salesforce offers quick deploy where any pipeline with validate step with unit test are eligibleOpsera 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 exaction execution a unique Deployment Job ID is generated which can be used and quick deploy can be performed.

Info

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.

Table of Contents
minLevel1
maxLevel7

Salesforce Quick Deploy Task Configuration

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

...

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

...

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

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 :

  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

...

  1. .

...

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 :

  1. ID provided for the validation job is unsuccessful/in-progress.

  2. ID provided for the validation job is not having test execution available.

  3. ID provided for the validation job is not having test coverage criteria (75%) met.

Q. Quick Deploy Task fails with below message

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.

Q. Quick Deploy Task fails with below message

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.