Travis CI and beyond?

Is there some recommendation about how to handle the closing of

The official story was that all free projects should be moved/migrated to

On the other hand there are trying to impose new constraints and restrictions:,now%20just%20two%20months%20away.

On I see a message "Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting." for a collective.* project.

I am confused...or is everyone moving on to Github Actions?

Either this or try to convince Travis to give you some credits for your open source projects. That's the "official" way.

The funny thing is that I see only thr plone and collecitive repos in my account but not the ones from my own Github account :clown_face::clown_face::clown_face:

For Volto we moved to gh actions some time ago and it works quite well for us. Though, it will be lots of work to migrate all existing projects from Travis to gh actions...

1 Like

@icemac created a tool to update CI and more for Zope repositories, maybe this could be adapted for Plone, too

1 Like

See shuts down Dec 31st

I think some of the ideas and the configuration could be used. But the rest might be too zopefoundation specific. We tried to use it for our gocept open source repositories and failed because they are too different.