| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
BuildStream commit bf8fc373d7711861129 (merge request 158) changes how
the SSH protocol works. New versions of BuildStream require these
changes to be able to interact with ostree.baserock.org over SSH. Old
versions of BuildStream will still be able to interact with it too.
|
|
|
|
| |
See https://github.com/ansible/ansible/issues/32812
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is different from the existing 'cache' repo in that we should
be careful what we push to it, and we should never delete things
from it once they have been made public.
Pushing to the releases repo should be done with ostree-push/receive
rather than BuildStream. I've set up the receive hook on the server.
The upstream repo of ostree-push/receive seems abandoned so I have
been using a fork: https://github.com/ssssam/ostree-push
See also:
https://listmaster.pepperfish.net/pipermail/baserock-dev-baserock.org/2017-September/013811.html
https://gitlab.com/baserock/definitions/merge_requests/58
|
|
|
|
|
|
|
|
|
| |
The version listed there was too old, modern BuildStream versions would
fail to push with this error:
Exception: Unsupported protocol version 1
Also make sure we don't put root-owned stuff into `/home/fedora`.
|
| |
|
| |
|
|
|
|
|
| |
Jonathan has done an armv8l64 bootstrap with BuildStream and I want to
get all of those artifacts into our cache.
|
|
|
|
|
|
|
|
|
| |
We now need a timer job to update the summary file, see:
https://buildstream.gitlab.io/buildstream/artifacts.html#summary-file-updates
I also updated BuildStream which changes the artifact push protocol.
Sadly the protocol isn't versioned yet so old versions will now fail to
push with weird errors.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
So far this is limited to the existing Baserock ops team, and a new
key that I will try to install into our GitLab CI configuration so
that build runners can push artifacts.
We don't to hand out access too widely because we currently don't do
any verification that the submitted artifacts actually corresponds to
the cache key that it's supposed to. This is fine as long as access
is limited to autobuilders that we control and trusted developers.
|
|
This is a new instance that can be used as an artifact cache by the
BuildStream build tool. Anyone can download artifacts over HTTPS.
Those given SSH access to the machine can write to the artifact cache
(this will likely be limited to automated build machines).
DNS is now set to point cache.baserock.org and ostree.baserock.org to
the HAProxy frontend.
The SSL certificate for the frontend-haproxy system has been regenerated
to include the cache.baserock.org and ostree.baserock.org domains.
|