search

dboehmer / coocook

👨‍🍳🦉 Web application for collecting recipes and making food plans
https://coocook.org/
Other
11 stars 2 forks source link

Inspect new Travis CI conditions and list next steps if required #134

Open dboehmer opened 3 years ago

dboehmer commented 3 years ago

There seem to be some changes at Travis CI.

Make clear what this means for Coocook and what we might need to do.

moseschmiedel commented 3 years ago

I think the essence is, that open source projects now have a limit of 10k credits, which is around 1000 minutes on Linux:

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

Credits can be renewed for free for open source, but has to be requested at travis-ci support:

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)

I think 1000 minutes ≈ 16h could be enough for Coocook for the start and when the credits run out, one could request more. But I don't know if this is to much effort for you @dboehmer. We could also look for a new CI/CD service...for example we could look into GitHub Actions.

moseschmiedel commented 3 years ago

A build of Coocook is between 12 and 16 minutes long. So 1000 minutes should allow us at minimum 62 builds. This approximately one build per week for one year. So requesting credits will be required sooner or later...

dboehmer commented 3 years ago

We could possibly optimize to speed up the build time. But 62 (or a bit more) won’t last that long: We already have far over 1000 commits in our repo. I can’t see a number of builds on Travis CI but build numbers seems to increase by 1 per build and the most recent build is 412.

I’m afraid of development going even slower when thinking about Travis CI “credits” before every Git push :disappointed:

But the most relevant question seems to be: How hard will it be to receive new “credits”? Do we need be nearly as relevant as OpenSSL or other projects mentioned?