This section provides detailed information about the changes and known issues in the current GitCentric release, GitCentric 2018.1.
Note: Note: Version 2017.1 is the last version to support 32-bit platforms. From the next release onwards, the GitCentric installer will support only 64-bit platforms.
The enhancements for this release include:
- You can now see the …/accurev/storage/site_slice/log/trigger.log output from the server_preop_trig.pl when an error occurs.
- Fixed the Gerrit review & settings URL sent in Gerrit review mails.
Changes in Release 2018.1
This section describes the changes and enhancements for GitCentric 2018.1.
Tip: In cases where an issue is identified with two numbers, 34987 (2788687), for example, the first represents the issue number in the AccuWork issue tracking system; the second, in parentheses, is the issue number in the SupportLine system used by Customer Care.
636572 - Deprecation note for support 32-bit
The current release is the last one to support 32-bit platforms. GitCentric installer will support only 64-bit platforms from the next release onwards.
1114925 - Bad error message when server preop trig blocks Git push
In earlier releases, if an AccuRev server preop trigger is set and the user doesn't have permission to push the code, GitCentric returned a bad error message. This has been fixed in the current release. Now the user will get the trigger output as the message’s preop trigger error.
1115883 - Add Gerrit email parameters info
In earlier releases, the Gerrit review & settings URL were sent incorrectly in the mail. This has been fixed in the current release.
The following fix was delivered as part 2017.1-HF1 release:
1109050 - Getting odd error when creating new repo
In earlier releases, the user received an ambiguous error while creating a new repository with an existing name. Now, the message for the storage write exception has been updated to "Cannot create repository <Repo Name> : Permission Denied."
The following fix was delivered as part 2017.1-HF2 release:
1109336 - GitCentric treats AccuRev elinks the same as slinks
In earlier releases, after a user commits a change to a file (which is of type symbolic link), no other committed changes could be pushed to GitCentric. This is fixed now.