1
by Brad Crittenden
Almost working buildbot master charm |
1 |
options: |
2 |
installdir: |
|
3 |
description: | |
|
4 |
The directory where the Buildbot master will be installed.
|
|
5 |
type: string |
|
6 |
default: /tmp/buildbot |
|
4
by Brad Crittenden
Incomplete work towards config directory checkout |
7 |
config-file: |
8 |
description: | |
|
9 |
A uuencoded master.cfg file. Use of this configuration is
|
|
10 |
mutually exclusive with the use of config-transport,
|
|
11 |
config-url. Use it like:
|
|
12 |
juju set buildbot-master config-file `uuencode master.cfg`
|
|
13 |
type: string |
|
14 |
config-transport: |
|
15 |
description: | |
|
16 |
The command transport for fetching the configuration directory
|
|
17 |
from the `config-url`. Must be one of [bzr, rsync]. If adding a
|
|
18 |
new supported protocol, ensure the program is installed in the
|
|
19 |
`start` hook and that it is properly handled in the
|
|
20 |
`config-changed` hook.
|
|
21 |
type: string |
|
22 |
config-url: |
|
23 |
description: | |
|
24 |
The location the buildbot master configuration is to be
|
|
25 |
fetched. It must be compatible with the `config-transport`.
|
|
26 |
type: string |
|
27 |
config-user: |
|
28 |
description: | |
|
29 |
The user for access to a restricted URL.
|
|
30 |
type: string |
|
31 |
config-private-key: |
|
32 |
description: | |
|
33 |
The private key for `config-user`.
|
|
34 |
type: string |
|
35 |
||
36 |