[SERVER-44427] Consider the appropriate components and roles for the build system and retag targets as appropriate Created: 05/Nov/19  Updated: 31/Jan/20  Resolved: 30/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Mathew Robinson (Inactive) Assignee: Mathew Robinson (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-45048 Cleanup artifacts.tgz and remove brid... Closed
Sprint: Dev Platform 2020-01-13, Dev Platform 2020-01-27, Dev Platform 2020-02-10
Participants:

 Description   

Over the course of PM-338 we've attempted to tag things such that they remain part of the component that corresponds to their old style aliases. We found some targets such as mongotmock and mongoebench that were part of aliases that did not necessarily make sense.

Now that the build system can be appropriately componentized we should consider not only what components should exist but what targets should belong to them. We should also produce a guidance document so developers in the future can determine when to create a new component and can get up to speed on what components we've already created.


Generated at Thu Feb 08 05:05:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.