Hello Faustin, On 10/18/21 5:02 PM, Faustin Lammler wrote:
The thing is, the runner managed by @stapbelerg is down because he's moving off Debian [2] and therefore has put the machine to another use.Why not using salsa shared runners and all the work made by the SalsaCI Team? Sorry if this was already responded many times before, there is maybe a very good reason.
Please see the page dedicated to our CI setup [1] for more details, everything is explained. To put it in a nutshell: we have a very special setup that allows us to prevent any regression (efficiently) with all go packages currently on the archive. But this setup requires a dedicated machine. That's why we can't use the SalsaCI shared runners. (at least for the moment)
I've work on creating Ansibles files [3] (which are now ready to use) that allows everyone to setup a Go capable runner and register it on Salsa.Excellent that you used Ansible to automate this process! I already have some comment on this but I guess that I could contribute directly in the repo (mainly on the Docker privilege mode that can be problematic in CI context IMO).
Please feel free to raise an issue on the repository to discuss these :) Also please note that the docker privileged mode is needed because we create an overlay in /cache/overlay/ to discard writes to /srv/gopath/src after the build is done.
I'll setup a VM on my infra and try to follow your setup documentation so I may have more feedback in the next days.
Many thanks!
The only thing: while some package took <10sec to be build (which is what is intended) some of them took >10mins, and that's not acceptable. I'm working on getting this issue fix before making the runner available for everyone.Yep, having a fast and reactive CI is something worth spending extra time on. Happy to help in debugging this too. More generally, if you need support or help on infrastructure questions, do not hesitate.
Thanks for the offer! The last struggle point is to reduce the build time. I'm currently profiling the build-tools to reduce the bottleneck as much as possible. I have some ideas in mind but little time lately to deal with it. We can discuss these issue on IRC if you want to brainstorm!
Cheers! Faustin
Cheers, [1]: https://go-team.pages.debian.net/ci.html -- Aloïs Micard <creekorful@debian.org> GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature