add GitHub Actions workflow to run easybuild-framework test suite#3039
Merged
akesandgren merged 9 commits intoeasybuilders:developfrom Oct 2, 2019
Merged
add GitHub Actions workflow to run easybuild-framework test suite#3039akesandgren merged 9 commits intoeasybuilders:developfrom
akesandgren merged 9 commits intoeasybuilders:developfrom
Conversation
…all_eb_dep.sh script
…d for Python 2.6)
…required ...') in Travis CI config
…ge, no longer needed with GC3Pie 2.6.2 release (thanks @riccardomurri!)
akesandgren
reviewed
Oct 1, 2019
akesandgren
reviewed
Oct 1, 2019
akesandgren
reviewed
Oct 1, 2019
akesandgren
reviewed
Oct 1, 2019
akesandgren
reviewed
Oct 1, 2019
Contributor
|
Going in, thanks @boegel! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This enables running the easybuild-framework test suite in the native CI that is now supported by GitHub through GitHub actions.
For now, I would like to have the tests running in both Travis and GitHub (since GitHub Actions is still in beta)
In the short term, we can change the setup to only keep testing with Python 2.6 in Travis (since it's a bit painful to do that in GitHub CI).
In the long term, switching to GitHub entirely is probably the best way forward...
This should significantly help with getting CI results more quickly, since: