Get desktop application:
View/edit binary Protocol Buffers messages
Configuration to integrate Spinnaker with your continuous integration system.
Used in:
Configuration to use AWS CodeBuild with Spinnnaker, for continuous integration.
Used in: ,
Whether AWS CodeBuild is enabled as a CI provider.
The list of configured AWS CodeBuild accounts.
Your AWS Access Key ID. If not provided, Spinnaker tries to find AWS credentials, as described at http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default
Your AWS Secret Key.
Configuration for an AWS CodeBuild account.
Used in:
The name of the account.
The AWS account ID that will be used to trigger CodeBuild builds.
If set, Spinnaker configures a credentials provider that uses the AWS Security Token Service to assume the specified role.
(Required) The AWS region in which your CodeBuild projects live.
Configuration to use Concourse with Spinnaker, for continuous integration.
Used in: ,
Whether Concourse is enabled as a CI provider.
The list of configured Concourse accounts.
Configuration for a Concourse account.
Used in:
The name of the account.
(Required) The username of the Concourse user to authenticate as.
(Required) The password of the Concourse user to authenticate as.
(Required) The URL at which your Concourse search is reachable.
Configuration for Fiat permissions. A user must have at least one of the READ roles in order to view this build account or use it as a trigger source. A user must have at least one of the WRITE roles in order to run jobs on this build account.
Configuration to use Google Cloud Build with Spinnaker, for continuous integration.
Used in: , ,
Whether Cloud Build is enabled as a CI provider.
The list of configured Cloud Build accounts.
Configuration for a Cloud Build account.
Used in:
The name of the account.
The name of the Google Cloud project in which to trigger and monitor builds.
The name of the Pub/Sub subscription on which to listen for build changes.
The path to a JSON service account that Spinnaker will use for credentials. You need this only if Spinnaker is not deployed on a Compute Engine VM, or if Spinnaker needs permissions not afforded to the VM.
Fiat permissions configuration. A user must have at least a READ role to view this build account or use it as a trigger source. A user must have at least one of the WRITE roles in order to run builds.
Configuration to use Jenkins with Spinnaker, for continuous integration.
Used in: ,
Whether Jenkins is enabled.
The list of configured Jenkins accounts.
Configuration for a Jenkins account.
Used in:
The name of the account.
(Required) The username of the Jenkins user to authenticate as.
(Required) The password of the Jenkins user to authenticate as.
(Required) The URL at which the Jenkins server is reachable.
Whether or not to negotiate CSRF tokens when calling Jenkins.
Fiat permissions configuration. A user must have at least one of the READ roles in order to view this build account or use it as a trigger source. A user must have at least one of the WRITE roles in order to run jobs on this build account.
Configuration to use Travis CI with Spinnaker, for continuous integration.
Used in: ,
Whether Travis is enabled.
The list of configured Travis accounts.
Configuration for a Travis account.
Used in:
The name of the account.
(Required) The URL at which to reach the Travis API (https://api.travis-ci.org).
(Required) The base URL at which to reach the Travis UI (https://travis-ci.org).
The GitHub token with which to authenticate against Travis.
Fiat permissions configuration. A user must have at least one of the READ roles in order to view this build account or use it as a trigger source. A user must have at least one of the WRITE roles in order to run jobs on this build account.
The maximum number of jobs the Travis integration will retrieve per polling cycle. Defaults to `100`.
The maximum number of builds Igor returns when querying for builds for a specific repo. This determines, for example, how many builds are displayed in the drop-down when a user starts a manual pipeline execution. If you set this too high, the Travis API might return an error for jobs that write many logs, so the default setting is only `10`.
The list of repositories that will be scraped. This is useful if your organization uses many repositories and you want to speed things up by scanning only a subset.
Configuration to use Werker with Spinnaker, for continuous integration.
Used in: ,
Whether Wercker is enabled.
The list of configured Wercker accounts.
Configuration for a Wercker account.
Used in:
The name of the account.
(Required) The address at which to reach your Wercker instance.
The personal token of the Wercker user to authenticate as.
The username of the Wercker user to authenticate as.
Fiat permissions configuration. A user must have at least one of the READ roles in order to view this build account or use it as a trigger source. A user must have at least one of the WRITE roles in order to run jobs on this build account.