Skip to content

Latest commit

 

History

History
44 lines (35 loc) · 1.83 KB

artifact.md

File metadata and controls

44 lines (35 loc) · 1.83 KB
Raw

Artifact Policy

All artifacts must be named, versioned, and retained in a repository.

Purpose

A name and a semantic version allows artifacts to be located in a repository. The name and a build version allows artifacts to be traced back to source code and potentially reproduced.

Procedures

Dependencies

  • Artifact dependencies are artifacts.
  • Versions in dependency tree should be pinned to ensure final artifact is immutable.

Releasable Artifacts

  • Only releasable artifacts may be promoted to production environments.
  • Releasable artifacts have a release semantic version (without -SNAPSHOT, -alpha, or -beta suffix).
  • Releasable artifacts are immutable.
  • The source code for releasable artifacts must be tagged in source control.
  • An inventory of released artifacts (with license and dependency information) should be kept to enforce license policy

All Artifacts

  • Must be semantically versioned.
  • Must be archived in a repository with the semantic version.

In-House Artifacts

  • Must be semantically and build versioned.
  • Must have source code in source control.
  • Must be queryable for their semantic version and dependency versions.
  • Must be queryable for their build version, potentially a git hash code.

Open Source Artifacts

  • Must be immutable.
  • Must be traceable.
  • Must have source code available.
  • Must have an appropriate license.

Commercial Artifacts

  • Must be immutable.

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.