b2c-code

You can deploy B2C Commerce cartridges using the b2c CLI by targeting a specific server and code version. This uploads your code directly to the target environment and manages the deployment lifecycle for development, staging, or production.

Yes, you can auto-upload B2C code changes during development using the watch command. The b2c CLI monitors local file changes and automatically uploads updated cartridges to your connected server or sandbox in real time.

The best way to manage B2C code versions for CI/CD is using b2c CLI commands to activate, reload, or delete versions. This supports pipeline automation by controlling code parity and version states across sandboxes and servers.

Yes, the b2c CLI supports listing and inspecting code versions across sandboxes and servers. You can use the list command to view, manage, and maintain code parity across different development, staging, and production environments.

You can delete or reload a B2C code version on a target server using specific b2c CLI commands. These actions support lifecycle management and allow you to control code parity and reload behavior during CI/CD workflows.