-
Notifications
You must be signed in to change notification settings - Fork 14
Configuration
cpjolicoeur edited this page Oct 7, 2010
·
26 revisions
Top-level (global) configuration settings should go into your cerberus/config.yml file. Project specific configuration settings should go into the respective cerberus/config/project.yml file.
All SCM options are placed under the top-level scm: setting
scm:
type: scm, git, cvs, perforce, darcs
url:
user_name:
password:
view: # for perforce only
branch: # for git only
All Builder options are placed under the top-level builder: setting
builder:
type: rake, rspec, rant, ruby, bjam, maven2
build_dir:
rake:
task:
ruby:
task:
ruby_path:
success:
failure:
brokeness:
maven2:
cmd:
task:
bjam:
build_dir:
cmd:
target:
All Publisher options are placed under the top-level publisher: setting
publisher:
active: mail, gmailer, jabber, irc, twitter, rss, campfire
on_event:
mail:
delivery_method:
address:
port:
domain:
user_name:
password:
authentication:
sender:
recipients:
on_event:
jabber:
jid:
port:
password:
digest:
recipients:
on_event:
irc:
nick:
server:
port:
channel:
on_event:
rss:
file:
on_event:
campfire:
url:
on_event:
twitter:
login:
password:
bin_path:
build_dir:
setup_script:
log:
enable:
changeset_url:
hook:
HOOK_NAME:
on_event:
action:
at_time:
bin_path:
publisher:
active:
on_event:
mail:
delivery_method:
address:
port:
domain:
user_name:
password:
authentication:
sender:
recipients:
on_event:
jabber:
jid:
port:
password:
digest:
recipients:
on_event:
irc:
nick:
server:
port:
channel:
on_event:
rss:
file:
on_event:
campfire:
url:
on_event:
twitter:
login:
password:
scm:
type:
url:
user_name:
password:
view: #for perforce only
branch: #for git only
builder:
type:
build_dir:
setup_script:
rake:
task:
maven2:
cmd:
task:
bjam:
build_dir:
cmd:
target:
log:
enable:
changeset_url:
hook:
HOOK_NAME:
on_event:
action:
at_time: