project:deploy
Deploys the folder containing your SuiteCloud project. The folder gets zipped before deployment, only including the files and folders referenced in the deploy.xml file.
If you run suitecloud project:deploy with no options, the project is deployed without applying installation preferences. Account-specific values are labeled as error messages and stop the deployment.
For installation script, installation preference, and translation collection objects, files referenced in their XML structure are also deployed, even if those files aren't part of the deploy.xml file.
Syntax
suitecloud project:deploy [--applyinstallprefs] [--accountspecificvalues (WARNING|ERROR)]
Options
|
Option |
Required / Optional |
Description |
|---|---|---|
|
--applyinstallprefs |
Optional for SuiteApps |
Applies the settings from the For more information, see Installation Preferences in the SuiteApp of SuiteCloud Project |
|
--accountspecificvalues |
Optional for ACPs |
Flags account-specific values as either a warning or an error. Enter If you set the argument value is to If you set the argument value to For more information, see Account-Specific Values Validation in SuiteCloud Projects.
Important:
If you don't specify the |
|
-- dryrun or -- dryrun |
Optional |
Runs a preview of your deployment process. Your project isn't deployed.
Important:
You can only use this option in non-interactive mode. |
|
-i or --interactive |
Optional |
Runs the command in interactive mode. |
|
-l or --log |
Optional |
Sets the deployment log file location, either as a directory or a file name. If you specify a directory, a default log file is created in that location.
Important:
If a log file already exists in that location, deployment log details are added to that existing file. |
|
--help |
Optional |
Prints the help for this command. |
Interactive Example
Here's a command that deploys a SuiteCloud project to an account using interactive mode and creates a deployment log:
suitecloud project:deploy
When you run the command, you're prompted to answer the following questions:
Do you want to apply installation preferences? > Yes No
What do you want to do if the project contains account-specific values? Display a warning > Cancel the process
Non-interactive Example
Here's a command that deploys an Account Customization Project to an account using the non-interactive mode. It also creates a deployment log:
suitecloud project:deploy --applyinstallprefs
Output Example
When you run the command, it produces an output that is similar to the following:
>suitecloud project:deploy
The project has been deployed without applying installation preferences.
DEPLOY SUMMARY
Status: SUCCESS
Steps: 18/18 successful
Validation Results: 0 error(s), 0 warning(s)
SDF Errors: none
Local Timestamp: 2026-07-15T10:02:47.515Z
Account: Wolfe Electronics
Role: Administrator
SuiteApp ID: com.netsuite.quarks
------------------------------------------------------------
Step 1: PROJECT_VALIDATION
Step 2: MANIFEST_VALIDATION
Step 3: DEPLOY_FILE_VALIDATION
Step 4: CUSTOM_OBJECT_VALIDATION
Step 5: CUSTOM_OBJECT_VALIDATION --- custcenter_sdftestframework_kyhd (center)
Step 6: CUSTOM_OBJECT_VALIDATION --- custevent1 (crmcustomefield)
Step 7: CUSTOM_OBJECT_VALIDATION --- custevent2 (crmcustomefield)
Step 8: CUSTOM_OBJECT_VALIDATION --- custform_2_mstrwlf_330 (addressform)
Step 9: CUSTOM_OBJECT_VALIDATION --- custinteg_d71c55db6be7 (integration)
Step 10: CUSTOM_OBJECT_VALIDATION --- customlist10 (customlist)
Step 11: CUSTOM_OBJECT_VALIDATION --- customscript_helloworldsuitelet (suitelet)
Step 12: FILE_VALIDATION
Step 13: FOLDER_VALIDATION
Step 14: TRANSLATION_IMPORT_VALIDATION
Step 15: TRANSLATION_REFERENCE_VALIDATION
Step 16: PREFERENCE_VALIDATION
Step 17: PLUG_IN_FLAG_VALIDATION
Step 18: CIRCULAR_DEPENDENCY_VALIDATION