e800b1e0f3
This simple command looks at every change's most recent patch set and reindexes the associated tracking information, based on the current trackingid blocks in gerrit.config. Administrators can run this command to reindex existing records after making changes. Bug: issue 124 Change-Id: I152ce430f84b70b6f84510f1abefc8da6037e746 Signed-off-by: Shawn O. Pearce <sop@google.com>
30 lines
706 B
Plaintext
30 lines
706 B
Plaintext
Gerrit Code Review - Server Programs
|
|
====================================
|
|
|
|
Server side programs can be started by executing the WAR file
|
|
through the Java command line. For example:
|
|
|
|
$ java -jar gerrit.war program [options]
|
|
|
|
[[programs]]Programs
|
|
--------------------
|
|
|
|
link:pgm-init.html[init]::
|
|
Initialize a new Gerrit server installation
|
|
|
|
link:pgm-daemon.html[daemon]::
|
|
Gerrit HTTP, SSH network server.
|
|
|
|
link:pgm-gsql.html[gsql]::
|
|
Administrative interface to idle database.
|
|
|
|
link:pgm-ScanTrackingIds.html[ScanTrackingIds]::
|
|
Rescan all changes after configuring trackingids.
|
|
|
|
version::
|
|
Display the release version of Gerrit Code Review.
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:index.html[Gerrit Code Review]
|