You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been dealing with long queue times for CI builds. This is at least partially because for each PR four jobs start, each of which takes at least 12 minutes. Since travis gives us at most five concurrent jobs, only one PR can be built at a time. This becomes worse if a PR is based on a branch on the main repo, since CI runs on those too.
Azure offers 10 free concurrent jobs. Seems like an easy win.
10 free concurrent jobs
Easier to do multiple checks per build (i.e. linting and testing can happen in the same build, but be independent checks)
Output looks easy to navigate, has good integration with github
We could test on windows (depending on how hard this is to set up)
(possible) Some projects seem to use multiple cores for testing
Cons:
New system, will take some time to learn
Maybe microsoft will start being evil again
The text was updated successfully, but these errors were encountered:
We've been dealing with long queue times for CI builds. This is at least partially because for each PR four jobs start, each of which takes at least 12 minutes. Since travis gives us at most five concurrent jobs, only one PR can be built at a time. This becomes worse if a PR is based on a branch on the main repo, since CI runs on those too.
Azure offers 10 free concurrent jobs. Seems like an easy win.
Cons:
The text was updated successfully, but these errors were encountered: