-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
use github actions #4035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use github actions #4035
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/webpack-docs/webpack-js-org/2didem5yc |
azure has good build prospects too, I guess we could try that too |
It is there a comparison between all 3 (or some more)? I know Actions will only give us 2000 minutes per month, right now in Travis (completely infrastructure) it takes 10 mins, so we will get 200 jobs per month, give or take. It is this better than Travis? |
@montogeek Thanks for the information, I just took it for granted that github provides open source projects unlimited time as it mentioned I'll do more research later. |
CI runs much faster now (before: ~16min, after: ~8min) after this pull request #4033, it's acceptable in my opinion, so I'll close this PR. |
@montogeek FYI, I've written an email to github for clarifying and here's their answer: |
I think in long term will be great to migration on github actions (a lot of features) |
Maybe we can enable github actions along with travis for a while to see how one compared to another. When we collect enough data we can make a final decision which to use. |
Good idea |
I will prefer GitHub actions just because everything will be here :) |
With cache enabled, the I think it's quite promising compared to travis: |
This reverts commit 97c5ea9.
Seems github actions can run multiple jobs simultaneously which bring a faster result than travis even though the |
Since I can't test the deploy job, I've included an empty |
With the new pricing model introduced recently in travis https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing, the time spent running CI is much longer than before now. Thus I'm going to merge this PR once the CI pass so we can monitor the performance of Github Actions along with travis. |
Travis provides 5 concurrent builds for open source builds, and it's sort of limited for a project like webpack documentation. This pull request #4032 was postponed for many minutes as there're other jobs running, and it's a waste of time. I'm wondering if github actions can improve the situation.