The following fixes were made for this release:
The Status Monitor, which displays synchronization information for branch-stream mappings, has been improved for GitCentric 2014.1:
The user interface and messages associated with the AccuRev Connector were enhance for GitCentric 2014.1 to improve usability.
The installer has a number of improvements, including:
In previous releases, the GitCentric bridge did not display the mount point tree correctly. This problem has been corrected in the current release.
An enhancement in GitCentric 2013.3 (31617) automated the specification of the GitCentric server’s URL and UUID. An enhancement in GitCentric 2014.1 ensures that these settings are checked (and, if necessary, reset) each time the GitCentric bridge is restarted.
Previous versions of GitCentric, including the GitCentric installer itself, relied on Git. GitCentric now uses an internal copy of JGit, removing the dependency on an installed Git.
GitCentric 2014.1 introduces several new tools that make it easy to explore the repository:
As part of this change, the GitCentric user interface has undergone several other changes to improve usability:
GitCentric now enforces the best practice of making an initial empty commit when creating a repository.
In previous releases, GitCentric used the HTTP protocol as the default for Git clone commands copied on the General panel of the Repositories page. GitCentric now uses the SSH protocol as the default for copied Git clone commands.
In previous releases, the bridge set the ACCUREV_HOME environment variable to <tomcat_install>/temp each time an AccuRev command was run. Using the /temp directory had the potential to interfere with the Secure Sockets Layer (SSL) protocol introduced in AccuRev 6.1. To resolve this problem, the GitCentric installation creates a new directory, <gc_installer>/AccuRevGitCentric/accurev, and the bridge now sets ACCUREV_HOME to it. If you have implemented SSL for your AccuRev installation, the SSL certificates must be placed in <gc_installer>/AccuRevGitCentric/accurev/.accurev.
In previous releases, GitCentric did not properly escape special characters in the XML replies to REST API calls initiated by the GitCentric bridge - typically success and failure messages - and this sometimes caused an error during GitCentric operations. This problem has been corrected in the current release.
In previous releases, pushes would fail if the same email address was associated with multiple commit authors, as could be the case when one user used the same email address across multiple servers. This problem has been corrected in the current release: GitCentric now includes the AccuRev Server ID when querying for the email address, which resolves most cases. In the event that a unique email address cannot be determined, GitCentric rejects the push and displays an error message indicating the reason.
In previous releases, the initial export operation that populates a Git branch mapped to an AccuRev stream would sometimes time-out when the AccuRev stream was the source. Rather than trying to log in the GitCentric user and trying the operation again, GitCentric would behave as if the operation succeeded, but creating multiple 0-length files in the repository as a result.
This problem has been corrected in the current release, and if the GitCentric user session times out during a lengthy operation, it attempts to log in the GitCentric user and try the operation again.
In previous releases, when security-related errors occurred (401 Unauthorized, 403 Forbidden, and 405 Method not allowed, for example) they were written only to the kandoGerrit.log file. In GitCentric 2014.1, security-related error messages are now displayed in a dialog box allowing for easier troubleshooting and diagnosis.
GitCentric 2014.1 uses Gerrit Code Review Version 2.7.
The ability to import the complete Git history of the repository into AccuRev, which was in Beta in the previous release, has been temporarily