[SERVER-75061] Run commit message validation earlier in commit queue process Created: 16/Mar/23 Updated: 20/Mar/23 Resolved: 20/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Will Buerger | 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 | ||
| Assigned Teams: |
Server Development Platform
|
| Participants: |
| Description |
|
Commit message validation is run as one of the first tasks once a patch has reached the front of the commit queue. It'd be nice if it ran at some point earlier to avoid waiting in a long queue just to realize the commit message was slightly off; perhaps it can be run when the patch is being created from the CLI, or when a patch first enters the commit queue |
| Comments |
| Comment by Alex Neben [ 20/Mar/23 ] |
|
While I agree this would be a nice to have I am not sure how we would do this without some sneaky new API from evergreen. It is impossible to tell a specific task it can run at any point in the commit queue and have the rest of the tasks wait until the end. Since the change is not hugely impactful I am going to close this for now but if evergreen added such an API we could be open to considering this task. |
| Comment by Matthew Lewandowski [ 20/Mar/23 ] |
|
Discussed in Evergreen Triage: Server owns this task, but can look into increasing its priority or running it as a required check for the PR instead. |