Simplified test buildout setup by not using plone versions. #71
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
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.
See issue #69.
buildout.cfgnow extendsbase.cfgandversions.cfg.travis.cfgby default extends both but has a slightly different code-analysis setup. The different setup may not make sense anymore, but that is how it was until now. code-analysis passes with both setups..travis.ymlwe do one run with standardtravis.cfg, and one allowed failure withtravis.cfgminus theversions.cfg. We could skip that and have just one job.So if we don't mind further simplification/unification then there is some room, and I can do that. But we can also merge as is, when Travis passes.