PATTERN Cited by 1 source

Module as versioned artifact

Description

Every code push to an ML module repository produces a versioned, immutable artifact that can be referenced by downstream workflows. Artifacts are tagged (e.g., latestAlpha, latest) to enable promotion semantics without redeploying infrastructure. Rollback is a tag-pointer change, not a redeployment.

This pattern separates the concerns of: - Building — CI produces the artifact on every push - Promotion — tagging moves an artifact through lifecycle stages - Execution — workflows reference artifacts by version or tag - Rollback — revert the tag pointer; no infrastructure changes needed

Mechanics

1. Developer pushes code to module repository
2. CI pipeline builds and publishes a versioned module artifact
3. Artifact is tagged (e.g., latestAlpha for development, latest for production)
4. Workflows reference modules by tag or explicit version
5. Rollback: retag to previous artifact version

Seen In

• sources/2026-06-10-atlassian-architecting-scalable-ml-platforms — ML Studio: 2,000+ modules, 200k+ monthly iterations; every push produces an artifact; teams own namespaces autonomously; dynamic CI/CD per module

(Source: sources/2026-06-10-atlassian-architecting-scalable-ml-platforms)