[SERVER-46100] Stitch support lib activities should all be in one task group Created: 12/Feb/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The current implementation of the stitch support lib tasks are split into two task groups: The first task group does the build and archive part, and then the second does the build and run of the tests. While this works, it isn't ideal. Because they are separate task groups, they can run independently on separate machines. This causes the second task groups build of the tests to basically rebuild the whole library. It would be better if this was just one task group with the three activity set to run serially on one machine. |