|
| 1 | +# summary |
| 2 | + |
| 3 | +Quickly deploy a validated deployment to an org. |
| 4 | + |
| 5 | +# description |
| 6 | + |
| 7 | +Before you run this command, first create a validated deployment with the "sf deploy metadata validate" command, which returns a job ID. Validated deployments haven't been deployed to the org yet; you deploy them with this command. Either pass the job ID to this command or use the --use-most-recent flag to use the job ID of the most recently validated deployment. For the quick deploy to succeed, the associated validated deployment must also have succeeded. |
| 8 | + |
| 9 | +Executing this quick deploy command takes less time than a standard deploy because it skips running Apex tests. These tests were previously run as part of the validation. Validating first and then running a quick deploy is useful if the deployment to your production org take several hours and you don’t want to risk a failed deploy. |
| 10 | + |
| 11 | +This command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your source with the versions in your org. |
| 12 | + |
| 13 | +# examples |
| 14 | + |
| 15 | +- Run a quick deploy to your default org using a job ID: |
| 16 | + |
| 17 | + <%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2 |
| 18 | + |
| 19 | +- Asynchronously run a quick deploy of the most recently validated deployment to an org with alias "my-prod-org": |
| 20 | + |
| 21 | + <%= config.bin %> <%= command.id %> --async --use-most-recent --target-org my-prod-org |
| 22 | + |
| 23 | +# flags.job-id.summary |
| 24 | + |
| 25 | +Job ID of the deployment you want to quick deploy. |
| 26 | + |
| 27 | +# flags.job-id.description |
| 28 | + |
| 29 | +The job ID is valid for 10 days from when you started the validation. |
| 30 | + |
| 31 | +# flags.use-most-recent.summary |
| 32 | + |
| 33 | +Use the job ID of the most recently validated deployment. |
| 34 | + |
| 35 | +# flags.use-most-recent.description |
| 36 | + |
| 37 | +For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most recent deployment validation was more than 3 days ago, this flag won't find a job ID. |
| 38 | + |
| 39 | +# flags.wait.summary |
| 40 | + |
| 41 | +Number of minutes to wait for the command to complete and display results. |
| 42 | + |
| 43 | +# flags.wait.description |
| 44 | + |
| 45 | +If the command continues to run after the wait period, the CLI returns control of the terminal window to you. To resume watching the deploy, run "sf deploy metadata resume". To check the status of the deploy, run "sf deploy metadata report". |
| 46 | + |
| 47 | +# flags.verbose.summary |
| 48 | + |
| 49 | +Show verbose output of the deploy result. |
| 50 | + |
| 51 | +# flags.concise.summary |
| 52 | + |
| 53 | +Show concise output of the deploy result. |
| 54 | + |
| 55 | +# flags.async.summary |
| 56 | + |
| 57 | +Run the command asynchronously. |
| 58 | + |
| 59 | +# flags.async.description |
| 60 | + |
| 61 | +The command immediately returns the control of the terminal to you. This way, you can continue to use the CLI. To resume watching the deploy, run "sf deploy metadata resume". To check the status of the deploy, run "sf deploy metadata report". |
| 62 | + |
| 63 | +# flags.target-org.summary |
| 64 | + |
| 65 | +Login username or alias for the target org. |
| 66 | + |
| 67 | +# flags.target-org.description |
| 68 | + |
| 69 | +Overrides your default org. |
| 70 | + |
| 71 | +# error.CannotQuickDeploy |
| 72 | + |
| 73 | +Job ID can't be used for quick deployment. Possible reasons include the deployment hasn't been validated or the validation expired because you ran it more than 10 days ago. |
| 74 | + |
| 75 | +# error.QuickDeployFailure |
| 76 | + |
| 77 | +Deployment %s exited with status code: %s. |
| 78 | + |
| 79 | +# info.QuickDeploySuccess |
| 80 | + |
| 81 | +Successfully deployed (%s). |
0 commit comments