-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
Use Case
As a... Mongoose developer
I want... to keep up with necessary CI changes
So that... the integration tests keep working as expected
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
Risks/Unknowns
- Can we unpin driver evergreen tools in general? How do we prevent them from unexpectedly breaking the mongoose CI? If we don't unpin, how do we ensure they get updated on a regular enough basis?
Acceptance Criteria
Implementation Requirements
- functional reqs, potential snafus to avoid, performance targets, etc
Testing Requirements
- unit test, spec test sync, etc
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- additional tickets to file, required releases, etc
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward
- is related to
-
NODE-6495 Allow easy pinning/unpinning of driver evergreen tools version in our CI
-
- Backlog
-