| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
- Move the configuration file to /etc/mason.conf
- Move the scripts to /usr/lib/mason/
- Mason will store the report in /var/mason/report.html
|
| |
|
|
|
|
|
|
| |
Now that we use the upstream trove, rather than local trove for git,
the report generator needs to be updated to reflect that.
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
