Replace travis testing by github actions #337
Closed
Conversation
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
If anything goes wrong, the source code is not destoyed.
christianlupus
force-pushed
the
dev/actions
branch
from
a5e397e to
9d8fc5c
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR replaces the travis-based testing (causing trouble, see #296) by a github action based one. This allows also docker-based local testing for quicker development cycles once set up.
You can have a look at my fork's results e.g. here how it works.
This should be extended and be considered a first step towards #233.
PS: I know this is a huge amount of commits. In fact, I needed to commit to trigger a rebuild on github. Most probably you need to look at the combined patch... All these commits should be squeezed at best.