Add Travis-ci as the continuous integration service for Boost.Graph #63
Conversation
This file contains hidden or 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
Closed
maelvls
force-pushed
the
add-continuous-integration
branch
3 times, most recently
from
0e1b6ec to
ca0814d
Compare
I thought it would be a great idea to have the test running from a "neutral entity" instead of having to checkout the pull request and cd libs/graph/test && ../../../b2 I saw that many other boostorg submodules had their own CI system: - compute relies on travis-ci - geometry uses circleci The major difference between circleci and travis-ci is the multi-threading supported by circleci. Both are free for open-source project (as of 2016/04/26). I chose travis-ci because I know how to configure it. As for geometry, we could also use coveralls.io to display the test covering reports and improve the quality/coverage of tests on boostorg/graph. IMPORTANT: a member of boostorg will have to add the repo boostorg/graph into travis-ci for it to work.
maelvls
force-pushed
the
add-continuous-integration
branch
from
ca0814d to
600398c
Compare
|
I don't see a downside to this. |
Belcourt
pushed a commit
that referenced
this pull request
Nov 3, 2016
) * Add travis-ci as CI for boostorg/graph repo. I thought it would be a great idea to have the test running from a "neutral entity" instead of having to checkout the pull request and cd libs/graph/test && ../../../b2 I saw that many other boostorg submodules had their own CI system: - compute relies on travis-ci - geometry uses circleci The major difference between circleci and travis-ci is the multi-threading supported by circleci. Both are free for open-source project (as of 2016/04/26). I chose travis-ci because I know how to configure it. As for geometry, we could also use coveralls.io to display the test covering reports and improve the quality/coverage of tests on boostorg/graph. IMPORTANT: a member of boostorg will have to add the repo boostorg/graph into travis-ci for it to work. * csr_graph_test won't pass unless -std=c++11 is enabled * Fixed gcc too old (4.6.3) using instead gcc-4.8 for -std=c++11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I thought it would be a great idea to have the test running from a
"neutral entity" instead of having to checkout the pull request and
I saw that many other boostorg submodules had their own CI system:
The major difference between circleci and travis-ci is the multi-threading supported by circleci. Both are free for open-source project (as of 2016/04/26). I chose travis-ci because I know how to configure it.
As for geometry, we could also use coveralls.io to display the test covering reports and improve the quality/coverage of tests on boostorg/graph.
IMPORTANT: a member of boostorg will have to add the repo boostorg/graph into travis-ci for it to work.
I tested this file against my fork. Here is the travis-ci part. It works great!
The only slight issue is that it takes ~10min to build and test, but it's totally fine.
Here is what displays when opening a PR: