project deploy pipeline validate (Beta)
Perform a validate-only deployment from a branch to the pipeline stage’s org.
This feature is a Beta Service. Customers may opt to try such Beta Service in its sole discretion. Any use of the Beta Service is subject to the applicable Beta Services Terms provided at Agreements and Terms.
The first time you run any “project deploy pipeline” command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the “org login web” command.
A validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.
| Flag Name (Long) | Flag Name (Short) | Description |
|---|---|---|
‑‑async | N/A | Type: Boolean Run the command asynchronously. The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run “sf project deploy pipeline resume”. To check the status of the deployment, run “sf project deploy pipeline report”. |
‑‑branch‑name | ‑b | Type: Value Required Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to. |
‑‑bundle‑version‑name | ‑v | Type: Value Version name of the bundle. You must indicate the bundle version if deploying to the environment that corresponds to the first stage after the bundling stage. |
‑‑concise | N/A | Type: Boolean Show concise output of the command result. |
‑‑deploy‑all | ‑a | Type: Boolean Deploy all metadata in the branch to the stage’s org. If you don’t specify this flag, only changes in the stage’s branch are deployed. |
‑‑devops‑center‑project‑name | ‑p | Type: Value Required Name of the DevOps Center project. |
‑‑devops‑center‑username | ‑c | Type: Value Required Username or alias of the DevOps Center org. |
‑‑json | N/A | Type: Boolean Format output as json. |
‑‑test‑level | ‑l | Type: Value Valid Values: NoTestRun, RunSpecifiedTests, RunLocalTests, RunAllTestsInOrgDeployment Apex testing level. Valid values are:
If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section “Running Tests in a Deployment” in the “Metadata API Developer Guide”. (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) |
‑‑tests | ‑t | Type: Value Apex tests to run when –test-level is RunSpecifiedTests. Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces. |
‑‑verbose | N/A | Type: Boolean Show verbose output of the command result. |
‑‑wait | ‑w | Type: Value Default value: 33 minutesNumber of minutes to wait for command to complete and display results. If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run “sf project deploy pipeline report”. |
Perform a validate-only deployment from the Staging branch to the Staging environment (sandbox):
Perform a validate-only deployment of all changes from the main branch to the release environment: