There are several parts that need to work together in a successful
GitCentric installation. Here is a list of things to double-check. Make sure that:
- ASSIGN_USER_PRIVILEGE is defined in
acserver.cnf for the
AccuRev Server, and that you restart the
AccuRev Server after defining or changing it.
- The two
.WAR files have expanded in the Tomcat
webapps directory, creating directories named
gitcentric and
kandoBridge.
- <gc_home>/dbsettings.conf exists and contains valid entries for the database port (typically
localhost:5075), and database username/password (typically
postgres |
postgres unless you change these for security reasons).
- Your
AccuRev Server contains properly installed and configured triggers files (see
Install the AccuRev Trigger).
- You clear your browser cache after updating to the latest
.WAR files.
Also, remember that
Git, unlike
AccuRev, does not track empty directories.
Finally, experienced Gerrit users may recognize that
GitCentric includes a
Gerrit Code Review installation, although some details may be modified or ignored in the
GitCentric environment. For example, certain code review installation values (such as the httpd jetty web server port setting) are not
used in the
GitCentric environment.