tarmac #29

Configuration

public_key

(string) Base64-encoded SSH public key

oauth_consumer_secret

(string) OAuth consumer secret

packages

(string) Space-separated list of extra packages to install.

group

(string) Group to run Tarmac under

tarmac

schedule

(string) Cron-format interval to run Tarmac

*/10 * * * *

lp_username

(string) Launchpad username to log in with

oauth_consumer_key

(string) OAuth consumer key

private_key

(string) Base64-encoded SSH private key

oauth_access_secret

(string) OAuth access secret

environment

(string) YAML mapping of environment variables to set for the Tarmac process.

user

(string) User to run Tarmac as

tarmac

branches

(string) YAML mapping of branches to watch, as a string. Each branch is represented as its own YAML map with the key being the name and the values being a mapping of Tarmac property keys and values. Relative paths for tree_dir will be rooted under /srv/$(service_name)/var/. For example: branches: | uci-engine: verify_command: ./run-tests commit_message_template: [r=<approved_by>] <commit_message> voting_criteria: Approve >= 1

log_file

(string) Log file location for Tarmac. If specified as a relative path, this will live under /srv/$(service_name)/.

tarmac.log

install_keys

(string) YAML list of GPG keys for installation sources, as a string. For apt repository URLs, use the public key ID used to verify package signatures. For other sources such as PPA, use empty string. This list must have the same number of elements as install_sources, even if the key items are all empty string. An example to go with the above for install_sources: install_keys: | - '' - ''

- "69985774"

install_sources

(string) YAML list of additional installation sources, as a string. The number of install_sources must match the number of install_keys. For example: install_sources: | - ppa:project1/ppa - ppa:project2/ppa

- ppa:tarmac/daily

oauth_access_token

(string) OAuth access token