The information below was written for a previous version of Armory Spinnaker (v1.13 and earlier). Please look here for documentation on the latest version.

Refer to the Spinnaker documentation for configuring Jenkins at

The information below has been deprecated.

What To Expect

This guide should include:

Continuous Integration (CI)

Spinnaker’s goal is to leverage existing CI solutions to build and produce an artifact that can be deployed.

Enabling Spinnaker to Communicate with Jenkins

To enable Spinnaker to communicate with your Jenkins instance you will need to edit your spinnaker-local.yml file. First prepare to configure Jenkins by finding your password or API Token. You can find your token here: http://${YOUR_JENKINS_URL}/me/configure.

Then configure your /opt/spinnaker/config/spinnaker-local.yml file and add the following:

    enabled: true
    enabled: true
      name: Name-of-Jenkins-Service
      baseUrl: http://${YOUR_JENKINS_URL}
      username: ${YOUR_USERNAME}
      password: ${API_TOKEN}

Make sure to restart the Igor service: sudo docker restart igor

Multiple Jenkins Masters

If you have more than one Jenkins master, you’ll need to edit your igor-local.yml.

  enabled: ${services.jenkins.enabled:false}
    - name: First-Master
      username: first-master-username
      password: first-master-password
    - name: Second-Master
      username: second-master-username
      password: second-master-password


Igor is an API that is responsible for executing and reading the state of jobs from Jenkins.

Verify Your Jenkins Configuration

You can see if you’ve configured your jenkins master correctly by querying Gate:

curl localhost:8084/v2/builds

You should see a response similar to:

  "Armory Jenkins",