JetBrains deployment actions use the active connection, selected code version, cartridge configuration, and credentials to upload code to SFCC instances.
Before your first upload
Complete Configuration and verify remote access. Confirm the active connection, selected code version, and discovered cartridges. Save local changes and run any build steps your project requires before uploading generated assets.
Deploy to one development sandbox
Select the target
Use Select Connection and Select Code Version in the toolbar. Confirm that these identify your development sandbox and the intended upload version.
Open Deploy Code
Select Deploy Code in the toolbar and choose the selected instance. Review the cartridges and modules listed in the confirmation dialog, together with the target code version.
Review cleanup behavior
Check the cleanup option before confirming. Full Cleanup of the Code Version clears the entire target version; with it unchecked, the deployment replaces matching cartridges and modules while leaving other items in the version untouched. Ensure the local source contains the files you intend to keep in the replaced items.
Deploy and check the result
Confirm Deploy and wait for completion. Open View → Tool Windows → B2C Sync Log to review the result. If a task fails, resolve the reported error before retrying.
Verify the changed page or behavior on the intended sandbox. A completed upload does not by itself activate that code version for the storefront.
Upload while editing
Use Auto Upload in the toolbar when you want local changes to be uploaded during development. Check its state whenever you switch targets. Turn it off when you want to edit without sending changes.
For a single item, use its upload action in the Project view context menu. Use Cartridge Management to check source discovery and cartridge scope.
More deployment options
Deploy Code also provides deployment configurations and multiple-target workflows. Start with one verified development target before configuring these. Review every destination and its code version before confirming a multi-target deployment.
If deployment fails
| What you see | What to check |
|---|---|
| No cartridges are listed | Confirm the project root and scan for new cartridges. |
| Authentication or permission error | Check the connection's account, hostname access key, and WebDAV permissions. |
| A pre-deployment task failed | Read the task output, fix the build, and retry. |
| Upload completed but the storefront is unchanged | Confirm the destination code version, server activation, site cartridge path, and any project-specific asset build. |
Continue with Debugging or Logs to investigate runtime behavior.