Travis config to test on the different django database backends. #145
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
|
@mattjegan Thank you for the contribution! Definitely a testing proactive approach I can get behind. |
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 all, I have added some config to
.travis.ymlto allow for testing on "most" of the Django database backends. I have included PostgreSQL, MySQL and SQLite3. The only default Django backend that is missing is Oracle. This can be included however it would mean pulling in this project and also a maintainer setting up an oracle account.The motivation for this change is issue #142 and to allow for earlier detection so that a broken release doesn't make it to PyPi.
As you can see on Travis it works well.