A Bitbucket file artifact is a reference to a file stored in Bitbucket.
Types of Artifacts
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 .
Docker image artifacts are references to images in registries, such as GCR or Docker Hub.
Rather than refer to a resource by a URI, you can embed the artifact’s contents directly into the reference field in Base64.
GCS object artifacts are references to objects stored in GCS buckets.
Git Repo artifacts are references to Git repositories that are hosted by a Git hosting service.
A GitHub artifact is a reference to a file stored in GitHub or GitHub Enterprise.
A GitLab file artifact is a reference to a file stored in GitLab.
An HTTP file artifact is a reference to a file stored in plaintext and reachable via HTTP.
Kubernetes Object artifacts are running, deployed Kubernetes manifests. This is in contrast to something like a GitHub file that only contains the specification of a deployable Kubernetes manifest.
A Maven artifact is a reference to a Maven artifact stored in a Maven repository.
An Oracle Object Storage object artifact is a reference to an object in an Oracle Object Storage bucket.
S3 object artifacts are references to objects stored in S3 buckets.