[CXX-500] Clean up mongo orchestration use in build system Created: 27/Jan/15  Updated: 13/Apr/15  Resolved: 01/Apr/15

Status: Closed
Project: C++ Driver
Component/s: Testing
Affects Version/s: None
Fix Version/s: legacy-1.0.1

Type: Task Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Done Votes: 0
Labels: legacy-cxx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

We should use mongo orchestration more cleanly in our build system. Specifically, the following things could be done better:

-MCI cleanup for mongo orchestration happens in 'post', which isn't quite right. Not all tasks start or even install mongo orchestration. For example the 'compile' task across os's will always complain about not finding a running mongo orchestration, or not having it installed. We should only try to stop mongo orchestration if it's been started in the current task.

-SCons tries to connect to mongo orchestration when it's just building the driver. Unless you're building client tests or integration tests it shouldn't be necessary to try to connect to MO.



 Comments   
Comment by Githook User [ 01/Apr/15 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: CXX-500 Only start mongo-orchestration from Scons when running examples
Branch: legacy
https://github.com/mongodb/mongo-cxx-driver/commit/060651048d82ae2cb8fb31696d1e2673fa80384f

Comment by Andrew Morrow (Inactive) [ 31/Mar/15 ]

https://github.com/mongodb/mongo-cxx-driver/pull/272

Generated at Wed Feb 07 21:59:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.