baserock/baserock/infrastructure.git - gitlab.com: baserock/infrastructure.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	baserock_ostree: Move to Ubuntu	Pedro Alvarez	2021-09-20	2	-46/+103
\|
*	baserock_ostree: Upgrade Buildstream to version 1.1.3	Pedro Alvarez	2018-07-29	1	-1/+1
\|
*	Stop using default.target in servicespedro/default_target_workaround	Pedro Alvarez	2018-04-03	4	-4/+4
\| \| \| \| \| \| \| \| \|	Use multi-user.target instead. There is a bug in systemd that makes it ignore the services in default.target.wants folder: https://github.com/systemd/systemd/issues/6334 This issue is still present in fedora 27, so this is the best workaround for now.
*	baserock_ostree: Reinstall BuildStream whenever source code is updatedsam/buildstream-update	Sam Thursfield	2017-11-23	1	-1/+2
\|
*	baserock_ostree: Update for changes in BuildStream	Sam Thursfield	2017-11-23	2	-5/+5
\| \| \| \| \| \| \|	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.
*	Work around Ansible 2.4.1 bug	Sam Thursfield	2017-11-23	1	-1/+5
\| \| \| \|	See https://github.com/ansible/ansible/issues/32812
*	baserock_ostree: Add 'releases' repo	Sam Thursfield	2017-10-27	7	-7/+72
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	baserock_ostree: Update version of BuildStream that we installsam/ostree-update	Sam Thursfield	2017-10-23	1	-2/+4
\| \| \| \| \| \| \| \| \|	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`.
*	baserock_ostree: Note that we're on Fedora 26 now.	Sam Thursfield	2017-10-23	2	-2/+2
\|
*	baserock_ostree: Update and fix the Ansible scripts	Sam Thursfield	2017-10-23	1	-5/+4
\|
*	Give Jonathan Maw push access to ostree.baserock.org	Sam Thursfield	2017-09-29	2	-0/+2
\| \| \| \| \|	Jonathan has done an armv8l64 bootstrap with BuildStream and I want to get all of those artifacts into our cache.
*	baserock_ostree: Update for changes in BuildStreamsam/update-ostree	Sam Thursfield	2017-07-21	4	-1/+34
\| \| \| \| \| \| \| \| \|	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.
*	baserock_ostree: Add the private GitLab CI key (encrypted)sam/ostree	Sam Thursfield	2017-07-13	1	-0/+167
\|
*	baserock_ostree: Enable write access	Sam Thursfield	2017-07-13	6	-2/+36
\| \| \| \| \| \| \| \| \| \| \|	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.
*	Add ostree.baserock.org system	Sam Thursfield	2017-07-13	3	-0/+92
	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.