Improve the CI pipeline workflow #396
Description
Vercel has the 1 concurrent limit for building the site.
As we had to run the linkinator on every single commit. In the GitHub action CI workflow, we're using amondnet/vercel-action action which triggers the build using Vercel infra.
Now taking the Vercel 1 concurrent limit for building the site and if there is a new change pushed into the commit the CI workflow would start but would stall at amondnet/vercel-action action as to wait for other builds which are queue in Vercel to get completed (which might take few minutes to an 1 hour) and during all that time the Github action would still continue to run hiting the API endpoint to get the build status.
There are couple of issues with our current approach:
- We're using VERCEL API TOKEN in the Github action which checks the build status on recurring basis
- If there are already 10 builds already in queue in Vercel, it might take a lot of time for it to get complete and Github action would continue keep running and ultimately get time-outed.
To mitigate this issue to certain extend, we've implemented concurrency group in CI workflow, it helped us tackle the above 2 issues but now the problem is that it simply ignores the build which gets triggered from various PRs.