Types of Artifacts

The contents of this page refer to alpha features in Spinnaker 1.6.

This means we are working on their stability and usability, as well as possibly adding or changing features. Expect rough edges, and file issues as needed.

While an artifact can reference any remote, deployable resource, we have first-class support for in the form of:

  • Parsing events from other services. For example, reading pub/sub messages from GCR images.

  • Credentials for downloading artifacts. For example, a GitHub access token to read repository contents.

  • Integrations with stages that require certain types of artifacts. For example, App Engine can only deploy a Docker image as a custom runtime, never an AMI.

The pages in this section serve to document the format Spinnaker expects these artifacts in, to make custom integrations with them easier. We recommend reading the artifact format first.

For information about how to use artifacts in pipelines, see About Spinnaker Artifacts.