Issue 1281 - Introduce module buildbot

modules/buildbot/manifests/master.pp

+# == Type: buildbot::master
+#
+# Manage Buildbot (http://buildbot.net/) master instances.
+#
+# Note that each instance implies the creation of a virtual Concat and
+# a virtual Concat::Fragment resource for setting up the master.cfg file.
+# One may either realize these resources (as done so by master::fragment
+# implicitly, for example) or use a custom approach for setting up the
+# configuration.
+#
+# === Parameters:
+#
+# [*basedir*]
+#   The base directory of the master, which can be configured elsewhere or,
+#   if it's ancestors are present, relied upon the builtin defaults.
+#
+# [*database*]
+#   Translates directly into the BuildmasterConfig['db_url'] configuration
+#   option within the master.cfg file.
+#
+# [*ensure*]
+#   Whether to setup the master (anything but 'absent' or 'purged') or

[Felix Dahlke, 2015/11/19 19:50:01]

Typo: "set up"

[mathias, 2016/01/20 16:13:52]

Acknowledged.

+#   remove the associated resources. Note that only 'purged' implies the
+#   removal of $basedir.
+#
+# [*http_port*]
+#   Translates directly into the port portion of the BuildmasterConfig's
+#   'buildbotURL', but may be used in other places as well.
+#
+# [*project*]

[Felix Dahlke, 2015/11/19 19:50:01]

Wouldn't it be simpler to have two separate parameters for title and url rather
than a hash containing both?

[mathias, 2016/01/20 16:13:52]

Yes, it would be simpler. Though the idea is that any other
project-related-meta-parameter can become a part of this hash, instead of
introducing a Puppet and Hiera parameter for every single item. Also, the other
parameters here are all in the system or admin domain, and I prefer not to mix
them up with a bunch of parameters that are merely irrelevant in this context.

However, giving this a second thought I figure it's not optimal having to
document recognized (and possibly re-named) keys in plain text without
semantics. The better idea is probably using the hash itself to initialize the
BuildmasterConfig ("c"), as-is, without name adjustments and dry, without
explicit per-option documentation (it's explained in the *.cfg anyway).

+#   A hash to optionally contain a 'title' (which translats into the config
+#   'title' option) and an 'url' (translates into the 'titleURL').
+#
+# [*slaves*]
+#   Local buildbot::slave records to setup with the master.

[Felix Dahlke, 2015/11/19 19:50:01]

Typo: "set up"

[mathias, 2016/01/20 16:13:51]

Acknowledged.

+#
+# [*slave_credentials*]
+#   Name => password pairs of e.g. remote build slaves.
+#
+# [*slave_port*]
+#   Translates directly into the BuildmasterConfig['slavePortnum'] option
+#   within the master.cfg file.
+#
+# [*system*]
+#   Any value beside 'false' will cause the master operations to also
+#   affect the buildbot::buildmaster service. Use this option to include
+#   the master instance with the system daemon.
+#
+# [*user*]
+#   The user to whom the master instance belongs to. Note that the user
+#   is not created implicitly by this setup, except if the creation is
+#   implied with any of the $buildbot::master_packages.
+#
+# === Examples:
+#
+#   buildbot::master {'primary':
+#     basedir => '/var/primary-buildmaster',
+#     project => {'title' => 'Awesomeness'},
+#   }
+#
+#   buildbot::master {'secondary':
+#     basedir => '/var/secondary-buildmaster',
+#     ensure => absent,
+#   }
+#
+define buildbot::master (
+  $basedir = "$::buildbot::master_directory/$name",
+  $database = "sqlite:///state.sqlite",
+  $ensure = 'present',
+  $http_port = 8010,
+  $project = {},
+  $slaves = {},
+  $slave_credentials = {},
+  $slave_port = 9989,
+  $system = false,
+  $user = $::buildbot::master_user,
+) {
+
+  if $ensure !~ /^(absent|purged)$/ {
+    ensure_packages($::buildbot::master_packages)
+    realize(File[$::buildbot::master_directory])
+
+    exec {"buildmaster#$title":
+      command => shellquote([
+        $::buildbot::master_runner,
+        'create-master',
+        $basedir,
+      ]),
+      creates => "$basedir/buildbot.tac",
+      require => [
+        File[$::buildbot::master_directory],
+        Package[$::buildbot::master_packages],
+      ],
+      user => $user,
+    }
+
+    Exec["buildmaster#$title"] <- Exec <|creates == $basedir|>
+    Exec["buildmaster#$title"] <- File <|path == $basedir|>
+
+    $config = "$basedir/master.cfg"
+
+    @concat {$config:
+      owner => $user,
+      require => Exec["buildmaster#$title"],
+    }
+
+    @concat::fragment {$config:
+      content => template('buildbot/master.cfg.erb'),
+      target => $config,
+    }
+
+    if !empty($slaves) {
+      create_resources('buildbot::slave', $slaves)
+      realize(Concat[$config])
+      realize(Concat::Fragment[$config])
+    }
+  }
+
+  if $system != false {
+    ensure_packages($::buildbot::master_packages)
+    realize(Concat['buildmaster'])
+    realize(Concat::Fragment['buildmaster'])
+    realize(Service['buildmaster'])
+
+    concat::fragment {"buildmaster#$title":
+      content => template('buildbot/buildmaster_fragment.erb'),
+      ensure => $ensure ? {'present' => $ensure, default => 'absent'},
+      notify => Service['buildmaster'],
+      order => 1,
+      target => 'buildmaster',
+    }
+
+    Service['buildmaster'] <~ Exec <|creates == "$basedir"|>
+    Service['buildmaster'] <~ Exec <|creates == "$basedir/buildbot.tac"|>
+    Service['buildmaster'] <~ Exec <|creates == "$basedir/master.cfg"|>
+
+    Service['buildmaster'] <~ File <|path == "$basedir"|>
+    Service['buildmaster'] <~ File <|path == "$basedir/master.cfg"|>
+  }
+
+  if $ensure == 'purged' {
+    file {$basedir: ensure => 'absent'}
+  }
+}