[SERVER-44873] Enable new Ninja builder on stable branches Created: 27/Nov/19 Updated: 06/Dec/22 Resolved: 17/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Dev Platform 2020-05-04 | ||||
| Participants: | |||||
| Description |
|
We would like to ensure that adopters of the new Ninja builder can use the same tool while working on backports or other maintenance tasks on older stable branches, so we should backport support as far as is possible and/or makes sense. At least, we should ensure that v4.2 offers it. This isn't being filed as a backport ticket because it will be easier to just take the finished product, rather than try to backport all of the individual tickets that have gone into the new Ninja builder. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 17/Apr/20 ] |
|
We intended this to ensure that we had coverage of master and the prior stable. However, with v4.4 branch made, this has already happened. |