Configure a Git Repo Artifact Account
This shows how to configure a Git repo artifact account so that Spinnaker can use an entire repo as a single artifact.
Configure Artifacts
Artifacts are remote, deployable resources in Spinnaker.
Artifacts are remote, deployable resources in Spinnaker. Depending on their “ type ”, they will need credentials to be downloaded or uploaded. These pages take you through configuring those credentials.
Configure a GitHub artifact account
Configure a GitHub artifact account so that Spinnaker can download files from GitHub.
Configure a GitLab artifact account
Configure a GitLab artifact account so that Spinnaker can download files from GitLab.
Configure Bitbucket Artifact Credentials
Spinnaker supports reading data from Bitbucket artifacts directly.
Configure Helm Artifact account
Spinnaker stages that consume artifacts can read from a Helm provider directly.
Configure HTTP Artifact Credentials
Spinnaker supports reading HTTP files directly for artifacts.
Configure Maven Artifact Credentials
Spinnaker supports artifacts stored in a Maven repository.
Configure S3 Artifact
Spinnaker stages that read data from artifacts can read S3 files directly.
Configuring GCS Artifact Credentials
Spinnaker supports using GCS objects as artifacts.
Configuring Oracle Object Storage Artifact Credentials
Spinnaker supports ORacle Object Storage as an artifact source.
Last modified July 7, 2021: docs(aws): Fixing formatting, minor changes (#110) (bd0359b)