Continuous Integration renovation #575
Closed
Conversation
This file contains 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
… into development
circli works, now tox GHactions should work, as fixed minor syntactic problem in GH workflow
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.
Hi there,
I was compelled to create a PR due to this internship application
As discussed in other related community driven neuroscience modelling projects, due to policy changes free travis continous integration is about to become unworkable for many people.
In this PR I have implemented two CI alternative worklows to choose from. The first is .circleci (see the second build success badge in the README.md below the travis one). The second is tox via Github Actions. I chose to adopt .tox/Github actions, as that was the choice of BluePyOpt. Circle-CI has its own portal, and overall it is a very similar feel to travis.