#16DELIVERYPACKAGE
Package
Create deployable artifacts
Medium
Overview
Package built code into deployable artifacts: container images, tarballs, or bundles. Tagged with version and commit info.
Why It Matters
Minimal production images. Non-root containers. Multi-stage builds strip dev dependencies.
The Risk
Bloated images increase attack surface. Running as root amplifies security breaches. Without proper tagging, you can't trace what's deployed or roll back reliably.
Implementation Components
A complete implementation of this capability includes:
- Container images or deployment packages
- Multi-stage builds to minimize image size
- Non-root user configuration
- Semantic versioning tags
- Git commit SHA embedded in artifact metadata
- Immutable artifacts - never rebuild with same tag
Implementation Pattern
- 1Choose artifact format
- 2Define packaging process
- 3Tag with version + commit hash
- 4Optimize for size
Tool Examples
These are examples, not endorsements. Choose what fits your context.
Dependencies
Requires (must have first)
Enables (unlocks)
Same Phase
Other capabilities in this pipeline phase