hiera/roles/buildserver.yaml - Issue 29325436: Issue 1281 - Introduce module buildbot

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Side by Side Diff: hiera/roles/buildserver.yaml

Issue 29325436: Issue 1281 - Introduce module buildbot (Closed)

Patch Set: Issue 1281 - Rebase branch buildbot on top of upstream Created Sept. 5, 2015, 11:27 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View unified diff | Download patch

OLD	NEW
(Empty)
	1 classes:

	2 adblockplus::buildserver:

	3 domain: buildbot.adblockplus.org

	4 is_default_domain: true

	5 project:

	6 title: Adblock Plus

	7 url: https://adblockplus.org/

	8

	9 adblockplus::buildserver::slaves:

	10 castus:
	Felix Dahlke 2015/09/29 14:04:21 I would vote for more descriptive names in line wi I would vote for more descriptive names in line with our usual naming scheme, e.g. "buildslave1" or maybe even "linuxbuildslave1". What do you think? mathias 2015/09/29 14:18:56 Sure, this is actually just meant as an example. N Show quoted text On 2015/09/29 14:04:21, Felix Dahlke wrote: > I would vote for more descriptive names in line with our usual naming scheme, > e.g. "buildslave1" or maybe even "linuxbuildslave1". What do you think? Sure, this is actually just meant as an example. Note that an adblockplus::buildserver::slaves key in the YAML files in module private will overwrite this one, but not become merged. And until we actually have some useful examples implemented I somehow struggle with finding more descriptive names. Maybe "foo" or "bar"? Felix Dahlke 2015/10/02 12:16:26 Can't we leave those out then? As you see, it conf Show quoted text On 2015/09/29 14:18:56, mathias wrote: > On 2015/09/29 14:04:21, Felix Dahlke wrote: > > I would vote for more descriptive names in line with our usual naming scheme, > > e.g. "buildslave1" or maybe even "linuxbuildslave1". What do you think? > > Sure, this is actually just meant as an example. Note that an > adblockplus::buildserver::slaves key in the YAML files in module private will > overwrite this one, but not become merged. And until we actually have some > useful examples implemented I somehow struggle with finding more descriptive > names. Maybe "foo" or "bar"? Can't we leave those out then? As you see, it confused me :D mathias 2015/10/02 13:47:39 Acknowledged. Show quoted text On 2015/10/02 12:16:26, Felix Dahlke wrote: > Can't we leave those out then? As you see, it confused me :D Acknowledged.
	11 ensure: 'present'

	12 system: true

	13 crixus:

	14 ensure: 'present'

	15 system: true

	16

OLD	NEW

« no previous file with comments | « no previous file | modules/adblockplus/files/nginx/buildserver.conf » ('j') | modules/adblockplus/manifests/buildserver.pp » ('J')