| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Failing to do this means that the deployment uses the wrong morphology,
because build will end up using the repo without the .git suffix, so it
will never update the cached version of the repo without it.
The version with the .git suffix is only updated on the initial
checkout, but is used by deploy, so it would pick up obsolete
morphologies and not include new changes.
Rubber-stamped-by: Richard Maw
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Now the timestamp of the last time we looked for any changes in
the definitions.git repository is put into the footer area. It
is highlighted for visibility.
This makes it easier to see that the mason system is still
running, but that there is nothing new to build.
|
| |
|
|
| |
This reduces flicker/churn when browsing a mason report page.
|
| |
|
|
|
| |
This prevents discovering changes, and then being unable to build them
because the local trove has not yet got them.
|
| |
|
|
|
| |
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
| |
|
|
|
|
| |
If the git remote update command fails, we assume it's because
we are unable to connect to the trove. This gets reported as a
networking issue, rather than as a failure.
|
|
|
The distbuild system can be configured to act as a CI controller.
Providing appropriate config makes it copy all the scripts and systemd
units out of the mason directory onto the target, such that it will
start building and testing the configured cluster morphology on boot.
|
