| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
More information at https://nvd.nist.gov/vuln/detail/CVE-2018-14912
|
| |
|
|
|
|
|
|
|
|
| |
This fixes an issue where some .morph files wouldn't display correctly,
because they'd contain a < character and the browser would think that
this was a tag.
I've added some docstrings as well.
Change-Id: I3c7252319a06cac04880f8b20596003fde531609
|
| |
|
|
| |
Change-Id: I6f2a8f173ee31f6ab652bbcd9b93306555ebf5c2
|
| |
|
|
|
|
|
|
|
| |
This is much less typing and gives us neater URLs!
The paths /baserock and /delta are also now specially redirected to
/cgit/baserock and /cgit/delta, for the benefit of the extra-lazy.
Change-Id: I9cda805c0a6134fb91595bbf8f3e74668d745327
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, when Trove mirrored an upstream repo, it would allow users
to push branches as long as they started with the trove-id. The
intention is to keep local changes in a separate namespace that can
co-exist with whatever branches the upstream repo has. This patch
extends this to tags, so that users can push tags to refs/tags/{{
trove-id}}/whatever.
This is necessary for the `morph anchor` command to work as expected
when the 'ref' fields of some definitions point to tag objects. Git
itself prevents pushing tags to 'refs/heads/...' so `morph anchor` must
be configured to push them to 'refs/tags/...'. Without this patch,
Gitano will prevent that as well, but with this patch, `morph anchor`
should be usable.
Repos in the Trove's own prefix (such as the baserock/ repos on
git.baserock.org, or the foo-trove/ repos on a Trove with trove ID
'foo-trove') are the only ones not considered to be mirrors, and
users can already push branches and tags wherever they want to in these
repos.
Change-Id: I06496ea6c5c57d3fae7e5750cf51e31bbd16d8d2
|
| |
|
|
| |
Change-Id: Ica0b1412ef402eaf2474288d54f1471f655d31c5
|
| |
|
|
|
| |
These settings had a meaning for the old implementation of
lorry-controller, but are ignored by the current implementation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
They where generated in trove.configure before.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Add a script that will create a `site` project containing the releases
repository when run. It will be run on boot by a systemd unit.
|
| |
|
|
| |
Signed-off by: Adam Coldrick <adam.coldrick@codethink.co.uk>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
