Still testing on Travis CI?

[ranocha]

https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing:

We love our OSS teams who choose to build using TravisCI and we fully want to support that community. However, recently we have encountered significant abuse of the intention of this offering. Abusers have been tying up our build queues and causing performance reductions for everyone. In order to bring the rules back to fair playing grounds, we are implementing some changes for our public build repositories.

• For those of you who have been building on public repositories (on travis-ci.com, with no paid subscription), we will upgrade you to our trial (free) plan with a 10K credit allotment (which allows around 1000 minutes in a Linux environment).
• You will not need to change your build definitions when you are pointed to the new plan
• When your credit allotment runs out - we’d love for you to consider which of our plans will meet your needs.
• We will be offering an allotment of OSS minutes that will be reviewed and allocated on a case by case basis. Should you want to apply for these credits please open a request with Travis CI support stating that you’d like to be considered for the OSS allotment. Please include:
  • Your account name and VCS provider (like travis-ci.com/github/[your account name] )
  • How many credits (build minutes) you’d like to request (should your run out of credits again you can repeat the process to request more)
• Usage will be tracked under your account information so that you can better understand how many credits/minutes are being used

It looks like you would need to request build time (again and again)...

I'm moving all of my Julia packages to GitHub actions instead of Travis CI.

[ketch]

That's too bad. Perhaps we can find another cloud service, or run our own CI server (as I did a long time ago). Of course, for something like Nodepy 1000 minutes would last quite a while, so sticking with Travis might also be okay.

[ranocha]

Will you notify the Clawpack team?