Simon Josefsson <[email protected]> writes: > Is this still true now? I see > > https://git.lysator.liu.se/nettle/nettle/-/jobs/4086 > > that lysator's shared runners appears to be used. I don't know their > availability, no problem keeping my runner in the configuration.
Ah, I hadn't noticed. When I initially enabled ci at git.lysator.liu.se, that shared runner failed the nettle jobs in ways I didn't understand, and appeared to require additional config. Good that it can be used now! I think some jobs are still picked up by your runner, most recent being https://git.lysator.liu.se/nettle/nettle/-/jobs/4060. It's good to have some redundancy. > Runners cache images, but gitlab.com has many runners so in practice > the end result vary. I wouldn't worry about this traffic. I would like to understand caching better (but it's more of an issue for gitlab at work; there it would be desirable to also let neighbor runners have a shared cache for all of container images, go packages, debian packages downloaded as part of tests, etc). > The pipeline for the mirror I added is green, without me doing anything > - so I think your configuration is good: > > https://gitlab.com/gsasl/nettle/-/pipelines Nice. > Given that gitlab.com/gnutls finally approved for the OSS Ultimate plan, > I suspect there is no point in having a gitlab.com/gsasl/nettle mirror > for pipelines, so I will remove the gsasl one. I agree, that seems like a waste of electricity. Regards, /Niels -- Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
