Spinnaker Artifacts - Legacy UI on Spinnaker

Artifacts from Build Triggers

Mon, 01 Jan 0001 00:00:00 +0000

Overview

When an external CI system triggers a pipeline, Spinnaker can use the CI build information to inject relevant artifacts into the pipeline. The instructions here assume that you have set up a CI system and are familiar with using property files to pass variables from CI builds to Spinnaker pipelines.

The extraction of artifacts from the build information is done via a Jinja template; the template uses the trigger as context and outputs a list of artifacts to inject into the pipeline. Spinnaker provides a set of standard templates to use for artifact extraction, which users can augment with custom templates.

Artifacts In App Engine (Legacy)

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts can be used for several things in the Google App Engine provider:

They can be used to reference a GCS bucket that contains source code to be deployed on Google App Engine.
They can be used to reference a docker image stored in Google Container Registry to be deployed on App Engine Flex.
They can be used to reference config files (such as app.yaml) to be used during deployment to App Engine.

Artifacts Referencing Source Code From GCS

To use an artifact to reference source code that is stored in a GCS bucket, use the “GCS” Source Type when configuring a Server Group.

Artifacts In Kubernetes (Legacy)

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts play an important role in the Kubernetes provider. Everything from the manifests you deploy, to the Docker images or ConfigMaps they reference can be expressed or deployed in terms of artifacts.

Manifests as artifacts

There are two ways to deploy a manifest:

The manifest is supplied statically to a pipeline as text
The manifest is supplied as an artifact

The image below shows a deploy stage that deploys a manifest stored in a GCS bucket:

Artifacts In Pipelines (Legacy)

Mon, 01 Jan 0001 00:00:00 +0000

Much of the behavior described here depends on looking up execution history in Redis. Deleting recent executions from Redis can cause unexpected behavior.

Now that you have an idea of what an artifact is in Spinnaker, you need to understand how it’s used within pipelines. An artifact arrives in a pipeline execution either from an external trigger (for example, a Docker image pushed to a registry) or by getting fetched by a stage. That artifact is then consumed by downstream stages based on pre-defined behavior.