Additional Features on Spinnaker

Configuring the Script Stage

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

Purpose

The Script stage lets you run an arbitrary shell, Python, or Groovy script on a Jenkins instance as a first class stage in Spinnaker. For example, you can use it to launch a test suite from a pipeline instead of doing it manually. Using the Script stage requires some additional setup after you add Jenkins to your Spinnaker deployment.

Prerequisites

To configure a Script stage, you need:

A running Jenkins instance at $JENKINS_HOST, with a Jenkins user profile set up with access to create jobs
A running Spinnaker instance, with access to configuration files, and in which you have set up Jenkins on Spinnaker

Configure Jenkins

Download the raw job xml config file with the command:

Enable Slack Support Channels

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

You can create an application and configure it with relevant data—application attributes.

Including a Slack support channel for an application is a configurable application attribute. This feature communicates with Slack’s conversations API to expose a list of available Slack channels in your workspace. The Slack support channel feature is supported by all providers.

Configuration

Gate

You need an API token associated with your Slack workspace for gate to receive a list of channels from Slack’s API. See the Slack documentation if you need to create a Slack token. Add this token in the config for gate’s encrypted secrets.

Notifications and Events Guide

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

Out of the box, Spinnaker allows you to configure the following types of notifications:

This is discussed in the Configuring Notifications section below.

Additionally, Spinnaker allows you to set webhooks for git triggers. See the Setting up Git Triggers in Spinnaker section.

You can also set Spinnaker to stream all its events to a downstream listener. See the Add a Webhook to Spinnaker section.

Spinnaker is also capable of handling cron-based triggers and detect changes in Jenkins builds and Docker images by enabling continuous integration configuration in spinnaker

User Data Files and Metadata

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

Spinnaker refers to data injected into instances started by Spinnaker as user data. The implementation and naming of this varies from provider to provider, but the resulting functionality is similar. In AWS, it is known as User Data . In GCP, it is known as Instance Metadata . The template file used to define the user data is called the user data file which is located on the Clouddriver server. Tokens are replaced in the user data file to provide some specifics about the deployment. Every instance started has environment variables are set according to the template and the deployment. This feature is currently supported with the AWS and GCP providers.