[SERVER-23806] Don't generate misleading version string in mongod log for patch builds Created: 19/Apr/16 Updated: 22/Apr/16 Resolved: 22/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Jonathan Reams |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Platforms 13 (04/22/16) | ||||||||
| Participants: | |||||||||
| Description |
|
Patch builds will include a local commit number in the version string if a local commit has been done, like "db version v3.2.5-4-ge266e7e". However if a local commit has not been done a misleading version string such as "db version v3.2.5" is generated. The --dirty flag to git-describe will avoid this by adding "-dirty" to the version string if the local source has been modified. |
| Comments |
| Comment by Jonathan Reams [ 22/Apr/16 ] |
|
this will be resolved by |