Travis CI matrix builds #352
Merged
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
…lidation (simply do a compile and distcheck)
… "default" to skip the docs (and try to pass distcheck)
… enable just manpages in default build
…o sequential if this fails)
…omprehensible in script code
|
Passes as of https://travis-ci.org/jimklimov/nut/builds/188968181 |
This was referenced Jan 4, 2017
…d hotplug (not hardcoded root paths)
This was referenced Jan 4, 2017
|
Closed (semi-)automatically as the PR #354 was merged and includes this commit. |
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 extends the basics of PR #351 and defines several build scenarios that would run in parallel - and provides a template for future similar customized tests. As detailed in issue #338 this adds several build scenarios to quickly see if a coding/Makefile error breaks the repo:
--with-all) is just a bit longer than "default-nodoc"These times might be improved by integrating the changesets (PR #353) which added support for
--with-doc=skipso that a (limited)make distcheckcan still be done and uncommenting the prepared lines; some of the benefit will come from not building even the manpages, and some will come from not installing the doc-processing packages in builds that don't care about them.After this is integrated, development in branches will have an easy way to define tests for features brought by the branch (e.g. some custom scenarios for DMF that are not relevant in codebases that do not have it yet).