Building Your Cartridge Stack

Each cartridge is built independently, uploaded, and then added to the cartridge stack. This approach means you can change and upload cartridges independently, as long as you develop against same code version. The command-line tools are designed to work in the top-level folder of each plug-in or cartridge repository. For example, watch only works for the directory in which you start it.

Cartridges provided by Commerce Cloud only have to be built once for each version and uploaded. You can create a separate build script for routine maintenance of cartridges you update and upload. In contrast, you could also create a lightweight script that lets you dynamically build and upload just the cartridges you're currently working on.

Next Step: Customizing Controllers and Routes