CI CD Setup

CircleCI configuration and publication

QQQ 4.0 release. Final 4.0.0 is available. See QQQ 4.0 for release scope and migration guidance.

Read the selected repository's .circleci/config.yml and pinned orb source before adapting CI. The 4.0 core candidate uses kingsrook/qqq-orb@0.6.0; other ecosystem repos may use different workflows. Copying a generic wiki template can skip required analysis or publish the wrong artifact.

Core publication gates

The candidate configuration has separate test/static-analysis workflows, release-candidate publication for release/*, and final publication for exact vX.Y.Z tags. Candidate and final publishing jobs require their static-analysis job. The actual configuration determines branch/tag filters, contexts, Java installation, signing, and registry behavior.

For 4.0 stabilization use the existing release/4.0.x branch. Inspect remote versions before choosing the next candidate number; do not assume every push successfully publishes or increments a candidate. A merge to main alone is not evidence that final artifacts exist.

Use authorized CI secret contexts for Maven publishing and signing. Keep secret values out of logs and repository files. Diagnose setup failures separately from compilation, test, coverage, and analysis failures. A job can fail before Maven runs.

Repository-specific delivery

Java libraries, frontend packages, and deployed websites do not share a universal publishing recipe. The marketing website uses CircleCI/Munitor to GHCR and consolidated GitOps/ArgoCD; do not replace that path with qqq-orb snippets or the retired standalone CD repository.

Core CI source · qqq-orb source · Release flow