XSF Discussion - 2021-06-16

https://daniel.haxx.se/blog/2021/06/14/bye-bye-travis-ci/ isn't XSF not eligible for the travis-ci free tier for the same reason?

XSF has commercial sponsors right?

moparisthebest, the sponsors help with the yearly xsf meeting colocated with the FOSS, as fas as I know.

moparisthebest: correct

I haven't even bothered to apply right now - last I checked their dashboard says we have, and have used, no credits

Even if it's just a UI bug, their free credits should last us months at least

MattJ, whose dashboard?

travis-ci

autobuilds or what jonas’ ?

I don’t quite understand the question

eevvoor, https://travis-ci.com/github/xsf

So according to that we've used 174 minutes in the past month, there are supposedly 10000 free minutes with a free plan, so we have a way to go

I think the answer is migrating to Github Actions whenever we can, before those minutes run out

In almost 5 years :-D

11:41:20]<MattJ> I think the answer is migrating to Github Actions whenever we can, before those minutes run out migrating from a FOSS solution to a proprietary incompatible spec format?

L29Ah, which is the FOSS solution?

MattJ: travis

How is it FOSS?

i don't understand your question; there are sources in their github, the license is specified as MIT in wikipedia

So I see, Wikipedia states "The source is technically free software"

Self-hosting isn't an option for us, especially since this looks like it is not made to be easily self-hosted

and I'm not aware of any other hosted Travis offerings

I'd welcome making gitlab the primary

but before we do nothing at all, we should move away from travis, and if it means github actions

As discussed, there's currently no rush... I would rather only migrate once

MattJ, do we have travis credits now? IIRC last time my PR wasn't CIed by travis due to missing credits

Which PR?

I don't see any PRs from you on relevant repos since February

IIRC that one wasn't travis'ed https://github.com/xsf/xeps/pull/1063

ahh, but that was not due credits

https://travis-ci.org/github/xsf/xeps/builds/772488939#L1746

but still, that does not shed a good light on travis, right?

Right, Docker

if they are reated limited by docker.com

This is a problem with Docker Hub, I guess authentication should be added to the job

I did request an open-source sponsorship from Docker, I don't think I've heard back yet

But that's not really related to this

well, it is related to travis currently (sometimes?) not being able to CI your PRs

No, it's not

iirc that's simply a distinction between whether you're authenticating to Docker Hub, or pulling over an unauthenticated connection

Unauthenticated pulls now have strict rate limits, which doesn't go well with CI systems obviously

I was referring to travis in the broadest sense, not just the service. If I understood you correctly, then we could adjust our travis configuration (or something) and it would work again

but it is not clear to me if this requires an open-source sponsorhip from Docker or something else

No, as I said, the open-source sponsorship from Docker is unrelated to this issue

I just correlated the two things in my mind, I shouldn't have mentioned it :)

ok, but then we have to add some (our?) docker hub credentials somewhere in the travis file to not run into this rate limit, right?

Likely there is a way in Travis to configure secrets

hmm, no, travis file sounds wrong, cause secret ✏

FWIW, how gitlab solved that issue is that they have a local docker image proxy you can use

I am sure github actions has something similar, travis may too

may just need extra configuration (and the credentials for that would be handed into the job or so)

Don't docker pull through cachces usually simply have an IP based allowlist?

and they are configured in the docker daemon json, so outside of the typical travis-ci.yml scope

flow, I work with the gitlab stuff daily. It hands you tokens.

our gitlab setup uses our docker pull through cache via configuring it in the docker daemon's json configuration file, no tokens involved

and I would expect that gitlab/travis simply would do the same, if they run their own docker cache, as it does not require any configuration from the users

ofc i could be wrong

in any case, the gitlab runner is not aware of the docker cache

(at least in the setup i know)

ah, the dependency proxy things seems to be token-less now. I recall you had to docker login into it in the beginning, maybe they changed that.

or, more realistically, the runner sets it up on its own

I have created the Q3 application page here: https://wiki.xmpp.org/web/Membership_Applications_Q3_2021

👍️

Thanks Alex

dwd, council?

On the Element my messages are lost...

XMPP <3

XMPP is also very good at loosing messages, şişio‎ 🤣️.

Just wait and enjoy.

And then hunt the bug.

:) Come dm