Skip to content
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

Move to GitHub Actions CI #348

Closed
rejuvyesh opened this issue May 19, 2021 · 4 comments
Closed

Move to GitHub Actions CI #348

rejuvyesh opened this issue May 19, 2021 · 4 comments

Comments

@rejuvyesh
Copy link
Member

travis.org is going away. Also IME GitHub Actions CI is much faster as well. More importantly it is way more flexible and we can setup integration and bechmarks tests using something like https://github.com/tkf/Run.jl as is done in https://github.com/JuliaFolds/Transducers.jl/tree/master/.github/workflows/ for example.

@lassepe
Copy link
Member

lassepe commented May 20, 2021

I'm in favor of GitHub Actions, especially for the speed. I think the workflows that are enabled by Run.jl would also work on travis, wouldn't they? Maybe I don't really understand what this package does. Doesn't it just enable a shared environment for some extra dependencies? I have looked at its README a couple of times in the past and I never really understood how this is different from just using the normal test facility supported by Pkg.

@rejuvyesh
Copy link
Member Author

Oh, I agree Run.jl by itself is not necessary. Was just pointing at an example!

@zsunberg
Copy link
Member

I have added Github CI on all the repos, but I haven't disabled travis or removed the badges yet.

@zsunberg
Copy link
Member

I'm going to close this and open another issue for removing the old stuff

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

No branches or pull requests

3 participants