Migrate away from travis-ci.org

[slonopotamus]

travis-ci.org is going to be shut down on December, 31:

https://docs.travis-ci.com/user/migrate/open-source-repository-migration#frequently-asked-questions

Q. When will the migration from travis-ci.org to travis-ci.com be completed?
A. In an effort to ensure that all of our users - whether you build open-source, public or private repositories - receive regular feature updates, security patches and UX/UI enhancements, we are announcing that travis-ci.org will be officially closed down completely no later than December 31st, 2020, allowing us to focus all our efforts on bringing new features and fixes to travis-ci.com and all of our awesome users like yourself on the travis-ci.com domain.

Q. What will happen to travis-ci.org after December 31st, 2020?
A. Travis-ci.org will be switched to a read-only platform, allowing you to see your jobs build history from all repositories previously connected to travis-ci.org.

Also, note that travis-ci.com, while being the most logical place to move to, has build time limits for public repositories:

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

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).

I saw that multiple projects (for example, major part of Asciidoctor ecosystem) moved from Travis to GitHub Actions in last month or two, though this is not a single option available nowadays.

[HonkingGoose]

Hi @ben have you seen this issue?

Summary: Travis CI from the .org domain is shutting down. This means that tests and builds will no longer work after December 31st, 2020.

Action is needed to either:

• Migrate to Travis CI on the .com domain on the "free" plan, and get a one-time credit of 1000 free build minutes on Linux.
• Migrate to Travis CI on the .com domain and ask Travis CI support to get you on their open source plan (it seems you get a certain quota/allotment, if you exceed the quota/allotment you will have to nudge them to give you more minutes).
• Migrate to GitHub Actions and get unlimited build minutes for free.

I just wanted to ping you to make sure that you have seen this issue. 😄

---

EDIT: I've changed the mention of 1000 free build minutes per month on Travis CI .com as that seems to be a one-time credit only, also mention the Travis CI's open source plan.

[slonopotamus]

get 1000 free build minutes on Linux a month from their free trial plan

I never saw Travis to say a month. According to my googling, I believe it is a one-time credit.

[HonkingGoose]

I never saw Travis to say a month. According to my googling, I believe it is a one-time credit.

I think you're right, the Pricing FAQ on https://travis-ci.com/plans says:

Why don't you have a Trial period?

New customers are assigned the Free plan by default. You will be given 10,000 credits to try out the system. Linux, Windows, macOS, FreeBSD builds all supported.

I don't see anything on their plans page that say that those credits get topped up for free...
So it seems that this is a one-time credit, if it's used up, it's gone.

---

But there is a way to get free credits for open-source projects that have public builds, if you ask them, according to a section on https://travis-ci.com/plans:

Free for open source. We love the Open Source Community, and to show how much we love it, upon validated request placed with our Support Team you may receive free OSS credits for your public builds.

Also it seems that you will have to ask for new credits each time you run out.
Direct quote from https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing:

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)

[jnavila]

I have a branch at https://github.com/progit/progit2-fr/tree/github-actions to start the migration. It is not workable yet, but the required work on it is not that much.

[slonopotamus]

Also it seems that you will have to ask for new credits each time you run out.

This

1. Feels inconvenient
2. Imposes a risk of Travis rejecting quota request for random reasons and progit2 ending up without a CI suddenly
3. Is unpredictable. You can't predict how many PRs will be opened against progit2 and when given credits will run out.

Though it's up to project maintainers to decide whether they want to go with travis-ci.com or not. Maybe they like Travis so much that want to go payed plan for OSS project.