summaryrefslogtreecommitdiff
path: root/distbuild.configure
Commit message (Collapse)AuthorAgeFilesLines
* Fix deploying a non-generic MasonSam Thursfield2014-09-301-2/+1
| | | | | | | | Fixed DISTBUILD_GENERIC check in distbuild.configure, and TROVE_ADMIN_NAME check in mason.configure Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk> Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
* Allow the the deploment of generic distbuild nodesPedro Alvarez2014-09-171-0/+5
|
* Use the new distbuild.configurePedro Alvarez2014-09-171-101/+62
|
* Put distbuild logs into /srv/distbuildbaserock/richardipsum/tegra-distbuild-systemRichard Ipsum2014-07-181-8/+15
| | | | | | | | | On distbuild we put logs into /srv/distbuild/. For a disbuild network we expect a large storage device to be mounted at /srv/distbuild, however the rootfs may be relatively small, so we want to put logs onto the large storage device to avoid filling up the rootfs. Symlinks to the logs are placed in /var/log as a convenience.
* Fix distbuild conf extensionbaserock/richardipsum/fix_distbuild_conf_extRichard Ipsum2014-07-111-7/+7
| | | | | The distbuild conf extension uses TROVE_ID where it should use TROVE_HOST. This only becomes a problem when TROVE_ID and TROVE_HOSTNAME are not equal.
* Prevent distbuild nodes from filling up their disksSam Thursfield2014-06-051-5/+2
| | | | | | | | Distbuild workers run `morph gc` before running a build, to remove stale artifacts, but it turns out that they were configured in such a way that the command didn't do anything. Because of this, it was possible for distbuild nodes to break due to filling up their disks with cached git repos and artifacts.
* distbuild: Set trove-id as well as trove-hostSam Thursfield2014-04-081-0/+1
| | | | | Otherwise, the trove ID is missing from the set of repo-aliases, so distbuild fails to build anything on the Trove.
* Add distbuild config extensionRichard Ipsum2014-03-281-0/+161