Hello team,
As you may have noticed pkg-go-tools/ci-config is currently running
over all Go repositories in order to apply the new Gitlab CI configuration
(and configure KGB webhook and tagpending). Sorry for the noise on IRC :{
The new Gitlab CI configuration use the Gitlab include feature [1]
which allow us to dynamically change the CI configuration without having
to update the d/gitlab-ci.yml file, so hopefully, this is the last time we
will ever need to bulk update the CI configuration. (thanks @zhsj for the tips)
Another good news: @faustin (in CC) has made available for us a beast VM (48cores,
30Gb RAM) to test the new runner setup, therefore the CI has been enabled again
for test the setup for ~1week period (enough time to gather metrics for DSA, analyse
bottlenecks, etc...). Thanks @faustin!
The runner will run the the defined period and will be shut down afterwards, and taking
advantage of the newly CI configuration, we will be able to disable CI for all Go repositories
(to reduce the noises with all these Gitlab CI errors emails) without having to bulk update
all repositories.
When we have a strong idea of the resources needed I intend to seek for hardware sponsor (either
DSA, or an external one).
In the meantime, if anyone face errors with the CI please report them :)
Cheers,
[1]: https://docs.gitlab.com/ee/ci/yaml/includes.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