Skip to content

Stop using Travis CI and AppVeyor #4053

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

Merged

Conversation

yutannihilation
Copy link
Member

It has been 3 months since we enabled GitHub Actions CI (#3862). While we still need to take care GitHub Actions CI time to time, it seems to catch the unintended changes reliably just as Travis CI and AppVeyor have been doing for years. So, I think it's okay to stop using Travis CI and AppVeyor now.

Copy link
Member

@karawoo karawoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine to me. We could also remove .travis.yml and appveyor.yml from .Rbuildignore, though I guess it doesn't really matter that much.

@yutannihilation
Copy link
Member Author

We could also remove .travis.yml and appveyor.yml from .Rbuildignore

Thanks! I forgot to do this.

@thomasp85 @clauswilke
Do you have any concern to stop using Travis CI and AppVeyor? If not, I'll merge this (though it seems we need to change some setting on AppVayor to actually deactivate it)

@clauswilke
Copy link
Member

I have no strong opinion one way or another.

@yutannihilation
Copy link
Member Author

Thanks, Claus. I'm merging this.

@yutannihilation yutannihilation merged commit 2edcec1 into tidyverse:master Jun 20, 2020
@yutannihilation yutannihilation deleted the ci/stop-travis-and-appveyor branch June 20, 2020 00:45
@yutannihilation
Copy link
Member Author

@thomasp85 @hadley
Could you disable the integrations with Travis CI and AppVeyor? We now rely only on GitHub Actions CI.

This was referenced Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants