[SERVER-59511] Improve output of validate_commit_message script Created: 23/Aug/21  Updated: 29/Oct/23  Resolved: 08/Sep/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: David Bradford (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: DAG 2021-09-20
Participants:
Story Points: 1

 Description   

When the validate commit message script fails, it can be difficult to find the issues. We should update the output to make it clear what caused the failure and provide some way to make that sounds out in the logs.


As a database contributor,
I want to easily be able to determine why validate-commit-message failed,
So that I can quickly fix the issue.


AC:

  • Some easy to spot marker makes it obvious where in the logs the validate_commit_message error is.
  • The failure message provided is clear and actionable.


 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 08/Sep/21 ]

Author:

{'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}

Message: SERVER-59511: Improve error messages in validate_commit_message
Branch: master
https://github.com/mongodb/mongo/commit/307cc81f1af0d00312e0fa802373b92cb60a579f

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