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

Clean up Travis config - ARM build only? #3049

Closed
IAlibay opened this issue Dec 1, 2020 · 1 comment
Closed

Clean up Travis config - ARM build only? #3049

IAlibay opened this issue Dec 1, 2020 · 1 comment

Comments

@IAlibay
Copy link
Member

IAlibay commented Dec 1, 2020

Follow up to #3036 and #3040

Once #3040 is merged (and follow ups; #3046, etc...) most of our CI builds will have been migrated away from Travis. The only thing that isn't possible at this moment are ARM builds.

Thanks to @tylerjereddy we have a few more units to use on Travis, if we use them conservatively for exotic platforms we can probably stretch it out until an alternative solution can be found.

I would suggest here possibly considering either a merge-only or a cron arm build so we can check that things run as expected.

Note: the credit spending on Travis has been turned off for now, once the Travis config has been cleaned up we can re-enable it.

@IAlibay
Copy link
Member Author

IAlibay commented Mar 14, 2021

Travis CI cron job from #3149 has now been set to a weekly run and works (https://travis-ci.com/github/MDAnalysis/mdanalysis/builds/220027210s). We can re-consider as merge only later (I suspect we might want to avoid this at the moment as we are likely going to get a large volume of merges during the GSoC period). -- closing

@IAlibay IAlibay closed this as completed Mar 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant