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 commit adds Travis testing to the GnuPG suite.
The GnuPG testing clones its prerequisites, tests the prerequisites, installs the prerequisites, and then builds and tests GnuPG. All components in the suite are tested through GnuPG.
Testing of GnuPG and components includes Linux, OS X, AMD64, PPC64, Aarch64 and s390x under both GCC and Clang. Additionally, older Linux (Xenial) and older OS X (El Capitan) are tested. Finally, Ubsan and Asan are tested.
The testing pipeline is revealing a lot of problems in GnuPG sources, from compile problems on PowerPC to undefined behavior and memory errors. You can find the results at Noloader | GnuPG fork, where the CI pipeline with Travis is in effect.
The immediate problem at the moment is the requirement for
--enable-maintainer-mode
when working from Git sources. For the purposes of testing the build and the code in a CI pipeline, maintainer mode is mostly irrelevant. We need to repeatedly build the suite in different configurations to ensure the suite builds and performs as expected. We don't need 28 or so builds that build the docs. Document building not only breaks every build, it also adds additional time to the build, wastes cpu cycles and wastes storage. A few--enable-maintainer-mode
are fine to test the feature for maintainers, but 28 or so is excessive.I think the project should provide better support for a Continuous Integration pipeline. Running Travis after a commit or every night would have caught all of the non-document errors present in the code. Also see Github sources are difficult to test in the issue tracker.