Time to remove Travis support?

Ryan Schmidt ryandesign at macports.org
Thu Nov 5 22:33:01 UTC 2020

On Nov 2, 2020, at 13:14, Mojca Miklavec wrote:

> If I understand correctly, we'll soon be unable to run any builds on
> Travis unless we pay for it (they are gradually moving existing
> customers to the new billing plan, so it's just a matter of time):
>    https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
> We cannot say that this wasn't expected, so maybe it's time to put the
> last nail in that coffin? I don't know if we can expand the OS version
> list in any of the other services (GitHub Actions or Azure), but it's
> ok even if we don't.

That announcement does also say:

> We love our OSS teams who choose to build and test using TravisCI and we fully want to support that community.


> 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 or discuss a renewable amount)

However given that Travis builds time out after 50 minutes and we often have builds that exceed that amount maybe we should just discontinue using Travis now.

On Nov 2, 2020, at 14:11, Ruben Di Battista wrote:

> As an alternative strategy I wanted to try to configure a Gitlab
> Runner with libvirt. Is it something you might be interested in?

I have no idea what you are proposing.

More information about the macports-dev mailing list