Fluent Commerce Logo
Docs

CI/CD Pipelines

Essential knowledgeCore knowledge to understand Fluent Commerce

Changed on:

9 Nov 2026

Overview

[Warning: empty required content area]

Key points

[Warning: empty required content area]

Stages

StageRuns onPurpose
Build and testEvery pushCompile rules, run unit tests, assemble the module archive
Static checksEvery pushWorkflow structure, lint and format
Deploy`dev` merges; release branches (manual)Configure and install the module
Post-deploy verificationAfter every deployRead back installed versions and fail on a mismatch
Tag`main` mergesName the release
Build and test steps run in parallel. Deploy stages consume the archive produced by the build step as an artifact and never rebuild it.

Sample bitbucket-pipelines.yml

Notes on the sample
  • `deployment:` on a stage gives every step in the stage that environment's variables and serialises deploys to it. If you forget it, the variables arrive empty or as literal `$NAME` text, which `profile.sh` detects.
  • Two install calls. Installing rules with `--skip-if-installed` avoids re-uploading a plugin version the account already has, while installing workflows with `--force` always reapplies them so the account cannot drift from the repository.
  • The release branch rebuilds once. In this sample the release-branch build uses the tag as its build identifier, so it produces the same version as `main`. If your controls require byte-for-byte promotion, publish the archive from the `main` build to an artifact store and have the release pipeline download it instead of rebuilding (see Verification and promotion).
  • Logs as artifacts. Every CLI call writes its own log file under `logs/`, so a failed deploy can be diagnosed from the pipeline run alone.
  • Build only what changed once the pipeline grows. Bitbucket's `condition: changesets: includePaths` can skip the Mystique steps when `frontend/` is untouched. Never skip a deploy-gating test this way.