I've been using GitLab CI and Travis CI interchangeably. But the recent cut to 400 pipeline minutes on GitLab CI might make it less attractive than Travis CI, even after the current change.
EDIT: Travis seems to take 10 credits per minute, with 1000 free credits per month. So it seems to be the least generous tool with 100 minutes per month vs 400 (GitLab CI) and 2000 (GitHub Actions).
One of my colleagues got that email. It seems to be saying something quite different to the blog post and the billing documentation, and I don't understand how they fit together.
Even if the email is accurate, which is the better scenario, though, 1000 credits is 100 minutes of Linux build time (or 50 on Windows, 20 on Mac). Which is not much for any but the smallest projects.
Comments
I've been using GitLab CI and Travis CI interchangeably. But the recent cut to 400 pipeline minutes on GitLab CI might make it less attractive than Travis CI, even after the current change.
EDIT: Travis seems to take 10 credits per minute, with 1000 free credits per month. So it seems to be the least generous tool with 100 minutes per month vs 400 (GitLab CI) and 2000 (GitHub Actions).
Where did you see the "per month" for Travis? The 10,000 free credits are a one-time trial from what I can see.
This is from a Travis CI mail I got today:
One of my colleagues got that email. It seems to be saying something quite different to the blog post and the billing documentation, and I don't understand how they fit together.
Even if the email is accurate, which is the better scenario, though, 1000 credits is 100 minutes of Linux build time (or 50 on Windows, 20 on Mac). Which is not much for any but the smallest projects.