I want to skip test cases run in production as we are already running those in validation

[gsanjana2712]

I am using this command for validation: sf project deploy validate --manifest ./delta/package/package.xml --post-destructive-changes ./delta/destructiveChanges/destructiveChanges.xml --target-org prod

In prod deployment pipeline: sf project deploy start --manifest ./delta/package/package.xml --post-destructive-changes ./delta/destructiveChanges/destructiveChanges.xml --target-org prod --ignore-conflicts

Now i want to skip test case run again in prod deployment pipeline.

If i go for quick deploy command 'sf project deploy quick --job-id 0Af0x000017yLUFCA2 --manifest ./delta/package/package.xml --post-destructive-changes ./delta/destructiveChanges/destructiveChanges.xml --target-org prod' then its showing that --manifest is invalid.

Please help me with command for above use.

Thanks!

[github-actions]

Hello @gsanjana2712 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[gsanjana2712]

output of sf version --verbose --json

» Warning: @salesforce/cli update available from 2.70.7 to 2.78.3.
{
"architecture": "win32-x64",
"cliVersion": "@salesforce/cli/2.70.7",
"nodeVersion": "node-v22.11.0",
"osVersion": "Windows_NT 10.0.26100",
"rootPath": "C:\Users\sanjanagupta\AppData\Local\sf\client\2.70.7-b4edef3",
"shell": "powershell",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.2.13 (core)",
"@oclif/plugin-commands 4.1.13 (core)",
"@oclif/plugin-help 6.2.19 (core)",
"@oclif/plugin-not-found 3.2.30 (core)",
"@oclif/plugin-plugins 5.4.22 (core)",
"@oclif/plugin-search 1.2.17 (core)",
"@oclif/plugin-update 4.6.17 (core)",
"@oclif/plugin-version 2.2.17 (core)",
"@oclif/plugin-warn-if-update-available 3.1.26 (core)",
"@oclif/plugin-which 3.2.20 (core)",
"@salesforce/cli 2.70.7 (core)",
"apex 3.6.7 (core)",
"api 1.3.2 (core)",
"auth 3.6.80 (core)",
"data 3.13.1 (core)",
"deploy-retrieve 3.15.20 (core)",
"info 3.4.27 (core)",
"limits 3.3.42 (core)",
"marketplace 1.3.7 (core)",
"org 5.2.9 (core)",
"packaging 2.9.6 (core)",
"schema 3.3.44 (core)",
"settings 2.4.9 (core)",
"sobject 1.4.46 (core)",
"telemetry 3.6.27 (core)",
"templates 56.3.33 (core)",
"trust 3.7.50 (core)",
"user 3.6.4 (core)"
]
}

[github-actions]

Hello @gsanjana2712 👋 None of the versions of sf you shared match the latest release.

Shared: 2.70.7
Latest: 2.78.3

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[WillieRuemmele]

sf project deploy quick only requires the ID of the previously validated deployment.

you'll pass all of your manifests to the project deploy valiadate command, and then use the returned ID in project deploy quick. So it would be a 2 step process like

1. sf project deploy validate --manifest ./delta/package/package.xml --post-destructive-changes ./delta/destructiveChanges/destructiveChanges.xml --target-org prod
2. sf project deploy quick --job-id 0Af0x000017yLUFCA2 --target-org prod