| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The Mason referred to here is the 1st version of the Mason continuous
delivery tool. There have been no instances of this for two years.
We have made two subsequent Mason implementations since then which don't
require coupling in Trove in order to work.
As well as removing unneeded configuration, this will fix the misleading
warning that users see on Git pushes:
remote: [git.baserock.org] Notifying Mason of changes...
remote: [git.baserock.org] Notification failed somehow
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Now UPSTREAM_TROVE is not mandatory to configure a Trove, and
if the value is not set, then the configuration of the lorry
controller (lorry-controller.conf) won't include any configuration
for an upstream Trove.
|
| | |
|
| |
|
|
|
|
| |
This allows downstream troves that only need to access publically
available content to be able to operate without configuring
ssh keys on the upstream trove.
|
| |
|
