[OPENDJ-5944] Use short hash for revisions in upgrade tool messages Created: 17/Jan/19  Updated: 28/Jul/20

Status: Dev backlog
Project: OpenDJ
Component/s: tools, upgrade
Affects Version/s: 7.0.0
Fix Version/s: None

Type: Improvement Priority: Trivial
Reporter: Cyril Quinton Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Epic Link: Miscellaneous 2020.Winter

 Description   

The upgrade tool displays version revisions:

* OpenDJ configuration will be upgraded from version
 4.0.0.0b7da454b79944f54e66daf3f591cefb5d77165b to
 7.0.0.d2edd2e1f9a769d214e8754bfe39a1b9ae2ac2d5
 * OpenDJ data will be upgraded from version 6.0.0 to
 7.0.0.d2edd2e1f9a769d214e8754bfe39a1b9ae2ac2d5
>>>> OpenDJ configuration was successfully upgraded from version
4.0.0.0b7da454b79944f54e66daf3f591cefb5d77165b to
7.0.0.d2edd2e1f9a769d214e8754bfe39a1b9ae2ac2d5

The revision is not really useful for the end user but can be a great piece of information for support. Considering support will often only receive the tool output, we cannot afford not showing the revision.
A good compromise (thanks Fabio Pistolesi and Chris Ridd) would be to use short hash versions and to use square brackets to improve readability:

 >>>> OpenDJ configuration was successfully upgraded from version
4.0.0 [0b7da454b79] to 7.0.0 [d2edd2e1f9a] 

An alternative would be to only show the revisions in upgrade.log file and to hide them in the console output. In case the upgrade fails, a message should remind the user to send this file to support.


Generated at Mon Mar 01 09:15:50 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.