| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: I309c183ce8b9ff9d0f5ac4807244547f2cc4ddf5
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Although we scan the keys of the Trove, we can only do this for the exact
hostname specified in TROVE_HOST. If the definitions being built point
to repos in the Trove using an SSH URL but with a different hostname
(e.g. as an IP address, or a differently qualified hostname) then the
distbuild will fail with a fairly opaque error:
ERROR: Build of xx failed: ERROR: Failed to update cached version of
repo ssh://git@.../xxx
Currently we expect distbuild to be deployed on a trusted private
network, so this change doesn't make it less secure. However, it would
be a problem in future if we want distbuild networks connecting to their
Trove across a public, untrusted network.
Change-Id: I6cf8b318cab8985e811b5ee5ac29df225b62270d
|
| |
|
|
|
|
|
|
| |
systemd warns about executable unit files. E.G. "Configuration file
/usr/lib/systemd/system/rsync.service is marked executable. Please
remove executable permission bits. Proceeding anyway."
Change-Id: I47721d7a78d6bbe87ebc171ff9b35db293d37e23
|
| | |
|
|
|
These files should be installed into distbuild worker and controller
systems using the install-files configure extension, by adding the
following line in the cluster morphology.
INSTALL_FILES: distbuild/manifest
These files were previously in the internal Codethink chunk repo
'distbuild-setup', and were installed by a Makefile.
|
