Skip to content

Move PR tests to GitHub actions #160

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

Closed
nicolasstucki opened this issue Dec 4, 2020 · 2 comments · Fixed by #175
Closed

Move PR tests to GitHub actions #160

nicolasstucki opened this issue Dec 4, 2020 · 2 comments · Fixed by #175
Assignees
Labels
enhancement New feature or request

Comments

@nicolasstucki
Copy link
Contributor

Lately, Travis has been slow/stuck while testing PRs.

I propose to we start testing in each PR on GitHub and Travis and later decide what to do.

@nicolasstucki nicolasstucki added the enhancement New feature or request label Dec 4, 2020
@MaximeKjaer
Copy link
Contributor

I think we should decide to move completely to GitHub Actions, and abandon Travis.

It seems that after recent announcements that Travis would be cutting back on OSS builds, they have been running only 400 builds at a time. This is down from 500 on November 19th, and it used to be a lot higher before November. This results in backlogs of 3-10K jobs on weekdays. I think the Travis slowness is unfortunately here to stay.

@MaximeKjaer MaximeKjaer self-assigned this Dec 9, 2020
@MaximeKjaer
Copy link
Contributor

MaximeKjaer commented Dec 10, 2020

I've started working on this: https://github.com/MaximeKjaer/vscode-scala-syntax/blob/gh-actions/.github/workflows/build.yml

I think we can also get deployments working from GitHub Actions, and it might be simpler than from Travis CI. This could also fix #147.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants