DATAMONGO-1411 - Enable MongoDB build on TravisCI. #358
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
Prepare issue branch.
Builds on TravisCI cause successful DNS reverse lookups for the used ServerAddresses so it's not reliable to check for the host part. Added missing author tags to the test. TravisCI supports as of now only MongoDB 2.4.2 when adding the MongoDB service to the config section. It's therefore required to upgrade the server. apt-get also starts the MongoDB server which is not obvious. Upgrade of profiles, removed promoted snapshot-versions, renamed mongo32-next to mongo32, added mongo33-next build profile. Original pull request: #358.
mp911de
force-pushed
the
issue/DATAMONGO-1411
branch
from
fd0b243 to
2acc373
Compare
christophstrobl
pushed a commit
that referenced
this pull request
Apr 26, 2016
We now start MongoDB server via apt-get instead of relying on the TravisCI managed 2.4.2 installation. Doing this we altered tests to just check on the port and not the host part of the URIs. Additionally we upgraded build profiles, removed promoted snapshot-versions, renamed mongo32-next to mongo32 and added mongo33-next build profile. Original pull request: #358
christophstrobl
pushed a commit
that referenced
this pull request
Apr 26, 2016
We now start MongoDB server via apt-get instead of relying on the TravisCI managed 2.4.2 installation. Doing this we altered tests to just check on the port and not the host part of the URIs. Additionally we upgraded build profiles, removed promoted snapshot-versions, renamed mongo32-next to mongo32 and added mongo33-next build profile. Original pull request: #358
christophstrobl
pushed a commit
that referenced
this pull request
Apr 26, 2016
We now start MongoDB server via apt-get instead of relying on the TravisCI managed 2.4.2 installation. Doing this we altered tests to just check on the port and not the host part of the URIs. Additionally we upgraded build profiles, removed promoted snapshot-versions, renamed mongo32-next to mongo32 and added mongo33-next build profile. Original pull request: #358
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.
Builds on TravisCI cause successful DNS reverse lookups for the used ServerAddresses so it's not reliable to check for the host part. Added missing author tags to the test.
TravisCI supports as of now only MongoDB 2.4.2 when adding the MongoDB service to the config section. It's therefore required to upgrade the server. apt-get also starts the MongoDB server which is not obvious.
Upgrade of profiles, removed promoted snapshot-versions, renamed mongo32-next to mongo32, added mongo33-next build profile.
Related ticket: DATAMONGO-1411