Spinnaker can listen to events and collect artifacts produced by external Continuous Integration (CI) systems.

Spinnaker can listen to events, and collect artifacts produced by builds in external Continuous Integration (CI) systems. These events can trigger Pipelines, and the artifacts can be used by Spinnaker’s image bakery to produce machine images.

For example, the Source to Prod codelab configures a Jenkins Job to produce a Debian package as an artifact that is handed to Spinnaker to build a VM image which Spinnaker deploys.

Currently, Spinnaker supports several CI systems which can be enabled and run independently of one-another, enumerated below.

Supported CI systems

These are the CI systems currently supported by Spinnaker:

See also hal config ci .

AWS CodeBuild

Spinnaker supports AWS CodeBuild as a continuous integration system.

Fiat Permissions

Igor, the Spinnaker service that connects to CI systems, requires READ and WRITE permissions, which are configured in Fiat.

Google Cloud Build

Spinnaker supports Google Cloud Build as a continuous integration system.


Travis CI

Spinnaker supports Travis as a continuou integration system.


Spinnaker supports Wercker as a continuous integration system.

Last modified May 4, 2021: docs(nav): collapse left nav (696c72c)