| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Previously if you enabled distbuild.configure but didn't set all of the
required variables, your deployment would fail. This has become much
more annoying with the introduction of the build-system family of
systems, which are indented to be suitable either as a local builder or
part of a distbuild network.
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Otherwise, the trove ID is missing from the set of repo-aliases, so
distbuild fails to build anything on the Trove.
|
|
|