CI on Spinnaker

AWS CodeBuild

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

Setting up AWS CodeBuild as a Continuous Integration (CI) system within Spinnaker allows you to:

trigger pipelines when an AWS CodeBuild build changes its phase or state
add an AWS CodeBuild stage to your pipeline

The AWS Codebuild stage requires Spinnaker 1.19 or later.

Prerequisites

AWS CodeBuild project

You need to have an AWS CodeBuild project. To create a project, follow the instructions on how to create a CodeBuild service role (AWS CLI) .

Fiat Permissions

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

Unless you have set fiat.legacyFallback to true (defaults to false) you will need to configure Igor CI services with Fiat READ and WRITE permissions.

Here is a Jenkins example:

jenkins:
  enabled: true
  masters:
  - name: <jenkins master name>
    address: http://<jenkins ip>/jenkins
    username: <jenkins admin user>
    password: <admin password>
    csrf: true
    permissions:
      READ:
      - foo
      - bar
      WRITE:
      - bar

In the example above, users with the foo or bar roles will be able to see the build master and use it as a trigger, and users with the bar role will additionally be able to trigger builds.

Google Cloud Build

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

Setting up Google Cloud Build as a Continuous Integration (CI) system within Spinnaker allows you to:

trigger pipelines when a GCB build completes
add a GCB stage to your pipeline

Prerequisites

GCP project

You need to have a Google Cloud Platform project with the Cloud Build API enabled. You can enable the API with the following gcloud command:

gcloud services enable cloudbuild.googleapis.com

Pub/sub subscription

Google Cloud Build sends Build Notifications when the state of your build changes. Spinnaker subscribes to these pub/sub messages so that it can…

Jenkins

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

Setting up Jenkins as a Continuous Integration (CI) system within Spinnaker lets you trigger pipelines with Jenkins, add a Jenkins stage to your pipeline, or add a Script stage to your pipeline.

Prerequisites

To connect Jenkins to Spinnaker, you need:

A running Jenkins Master at version 2.x, reachable at a URL ($BASEURL) from where Spinnaker runs.
A username/API key ($USERNAME/$APIKEY) pair able to authenticate against Jenkins using HTTP Basic Auth, if Jenkins is secured. A user’s API key can be found at $BASEURL/user/$USERNAME/configure.

Add your Jenkins master

Add the following to igor-local.yml to enable Jenkins;

Travis CI

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

You can configure Spinnaker to use Travis CI as your Continuous Integration system, trigger pipelines with Travis, or add a Travis stage to a pipeline.

Prerequisites

You need a Travis user with an API access token so that you get only the repos you should see.
That user needs adequate access in GitHub to trigger builds.

Add your Travis CI master

Enable Travis CI in igor-local.yml

travis:
  enabled: true
  masters:
  - name: someName
    baseUrl: https://travis-ci.com
    ## Address IS Required but MAY not be actually used anymore
    address: https://api.travis-ci.com
    githubToken: patUse
    numberOfJobs: number to poll for each cycle

It is recommended to use encrypted secrets for password information in the above