AccuRev Git Server UI Help

AccuRev Git Server is a new web application that enables developers to clone, push, and pull source code to and from AccuRev depots and streams using Git or any Git-compatible IDE or desktop application.

Benefits of AccuRev Git Server

Using the Git Server’s web interface, developers can browse for project repos, select stories to work on, and perform peer code reviews. Team leads and administrators can configure the Git Server, create new repos, view user access permissions, and read and download repo access logs.

The AccuRev Git Server provides the below following benefits :

Requires no client-side software other than Git version 2.31 (or higher).
Supports branches and tags.
Provides Git users with a full transaction history from AccuRev from the time that the AccuRev Git Server was instantiated.

Introduction of AccuRev Git Server

The AccuRev Git Server is included in the AccuRev full server and web server installs. No installation is required on client machines. The Git Server sits between Git users and the AccuRev server, and it interacts with AccuRev through the AccuRev Git Client. The Git Server is configurable via a web interface, and it has no dependency on triggers.

AccuRev streams are accessed using Git HTTP/S URLs. The system administrator creates a Git repo for an AccuRev stream, and then users can clone that repo. The Git Server supports task-based development using AccuRev change packages, in both the web interface and the CLI. Users can select issues to associate with push operations.

The commit history is shared between AccuRev and Git users. Commits on the master branch are pushed to the AccuRev stream corresponding to the Git repo and are visible in stream and element histories. Conversely, a fully materialized transaction history from AccuRev is visible to Git users:

The Git Server creates commits to reflect the changes inherited from upstream changes or from crosslinks. (This requires that the NOTIFICATION_LEVEL in acserver.cnf be set to 15.)
The git log command shows the full history since the Git repo was created.

Access control over Git repos is based on AccuRev stream ACLs. Access logs, visible to Administrators in the web interface, provide an audit trail of clone, push, and pull operations.

Pulse Code Review, initially introduced in release 7.3, is also included with full and web-only installs. It enables users to easily conduct code reviews on AccuRev issues (change packages). Code reviews are accessible through Pulse’s web interface, and also through the AccuRev GUI (AccuWork) and the AccuRev Git Server web interface. The Git Server displays the latest status of code reviews for issues in a repo’s change package.

Known issues

This section describes known issues in the AccuRev Git Server.

Cannot create a Git repo for a stream whose name contains spaces

In AccuRev 7.4, it is not possible to create a Git repo for a stream whose name contains spaces. This issue will be fixed in a future release.
AccuRev Git Server is not supported on CentOS 6

The AccuRev Git Server is not supported on CentOS 6 because the underlying AccuRev Git Client requires glibc v2.14, and CentOS 6 only supports glibc v2.12. If your AccuRev server is installed on CentOS 6, you can provide support for Git users by doing a separate AccuRev Web Server install on a different platform and having it connect to the CentOS 6 AccuRev server.