Build delays for open source project

[native-api]

As was pointed out in Builds hang in queued state - #6 by Montana linked to earlier in this topic, Travis is moving workers from travis-ci.org to travis-ci.com in preparation to fully close .org (or rather, make it read-only) around the New Year.

Travis CI Documentation

So you need to migrate to .com to stop experiencing delays. Note the caveats:

How to migrate from .org to .com in the light of .org shutting down?

You may want to consider migrating across to .com sooner rather than later How do we do that? OK, I managed to do this for my repos… I wish I recorded a screencast so I could tell you exactly what I did, becuase it involved some confusing steps, which don’t always match the travis documentation. But basically, you have to go to: => Go to https://travis-ci.com/account/repositories If you have a ‘migrate’ tab there, it will list your repos on travis-ci.org and let you migrate them. If y…

Will builds' logs be migrated upon .org -> .com migration?

It’s still the case that history is not fully migrated. The old builds are shown, but not their logs. Is there a target for when it will be migrated? When ready, will already-migrated repos have the history back-filled, or will only new migrations have history migrated?

.org -> .com migration unexpectedly comes with a plan change for OSS. What exactly is the new deal?

Oh hey though. I just realized, it turns out that open source will no longer be offered free service on travis-ci.com either. In case some of you had missed the announcement. https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works I had realized my builds stopped working on .org [1] , and was moving them all over to .com – where they started working as expected again – but I hadn’t realized that was just buying me a tiny bit of time. It looks lik…