- Get Started
- Functionality
- Learning
- Extension
- Dev Tooling
- APIs
- Releases
Changed on:
15 Nov 2026
`modules/`. A module should install identically into any account. Put retailer IDs, endpoints and environment-specific setting values in `cicd/configs/` or in pipeline variables.`-v <version>`, `FLUENT_PROFILE`) and never read `BITBUCKET_*` variables directly. The pipeline file maps CI variables onto script inputs, so the same scripts run locally and in any CI system.`modules/*/dist/`, `target/` and `logs/` are produced by the build and must never be committed.| Symptom | Cause | Guard |
| Deploy is green but rules did not change | Rules JAR version differs from `module.json`, so the CLI skipped the upload | Have `build-module.sh` fail on a version mismatch (Modules) |
| Deploy is green but a workflow did not update | CLI logged a validation or permission error and exited 0 | Wrap every CLI call with `fluent-cli.sh` (CLI) |
| Opaque 401 partway through a deploy | Step ran without `deployment:`, so the credentials were empty or literal `$NAME` text | Check all variables before calling the CLI (profile.sh) |
Error log shows `{ errors: [Array] }` | Default `util.inspect` depth | Preload `node-deep-inspect.cjs` |
| An old commit no longer builds the same way | Floating Node or CLI version | Pin exact versions in `prepare.sh` |
`mvn test` fails on a clean checkout before any test runs | Reactor modules unpack sibling JARs that only `package` produces | Build with `mvn package` |
| A hotfix disappears on the next release | Fix was made in the environment, or only on the release branch | Detect drift; fix in `dev` first, then cherry-pick |
| Two merged PRs break dev together | Each PR was tested against an old `dev` | Use a merge queue |
| Pipeline variables leak into logs | `set -x`, or echoing a command line that includes a password | Never trace credential-bearing steps; report variable names, not values |
| Deploy installs into the wrong retailer | Retailer list derived from files left in the checkout by another run | Read retailers from one variable (`FLUENT_RETAILERS`) only, with no fallback |
| CLI upgrade makes the error wrapper miss failures | Log message wording changed | Re-check `FAIL_PATTERNS` on every CLI upgrade |
1.
2├── bitbucket-pipelines.yml
3├── fluent-cli.sh # CLI wrapper that fails on swallowed errors (see 03)
4├── cicd/
5│ ├── prepare.sh # installs pinned Node + Fluent CLI
6│ ├── profile.sh # creates the CLI profile from pipeline variables
7│ ├── node-deep-inspect.cjs # makes CLI error payloads readable
8│ └── configs/ # committed per-retailer module configs
9│ └── module.config.<RETAILER>.<module>.json
10├── modules/
11│ └── acme-extensions/
12│ ├── plugins/ # Maven reactor for rule plugins
13│ │ ├── pom.xml # <revision> holds the authored version
14│ │ └── rules/
15│ │ └── acme-rules/ # rule classes + unit tests
16│ ├── resources/
17│ │ ├── module.json # module metadata, rule list, dependencies
18│ │ ├── module.config.json # config schema / defaults
19│ │ ├── workflows/
20│ │ ├── settings/
21│ │ └── rules/ # prepackaged dependency JARs, if any
22│ ├── scripts/
23│ │ └── build-module.sh # builds plugins, assembles and zips the archive
24│ ├── CHANGELOG.md
25│ └── README.md
26├── frontend/
27│ └── acme-mystique-plugin/ # custom Mystique components (see 08)
28└── tests/
29 └── e2e/ # live end-to-end cases against a dev account