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>
52 lines
1.1 KiB
Plaintext
52 lines
1.1 KiB
Plaintext
ScanTrackingIds
|
|
===============
|
|
|
|
NAME
|
|
----
|
|
ScanTrackingIds - Rescan changes to index trackingids
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'java' -jar gerrit.war 'ScanTrackingIds' -d <SITE_PATH>
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Scans every known change and updates the indexed tracking
|
|
ids associated with the change, after editing the trackingid
|
|
configuration in gerrit.config.
|
|
|
|
This task can take quite some time, but can run in the background
|
|
concurrently to the server if the database is MySQL or PostgreSQL.
|
|
If the database is H2, this task must be run by itself.
|
|
|
|
OPTIONS
|
|
-------
|
|
|
|
-d::
|
|
\--site-path::
|
|
Location of the gerrit.config file, and all other per-site
|
|
configuration data, supporting libaries and log files.
|
|
|
|
\--threads::
|
|
Number of threads to perform the scan work with. Defaults to
|
|
twice the number of CPUs available.
|
|
|
|
CONTEXT
|
|
-------
|
|
This command can only be run on a server which has direct
|
|
connectivity to the metadata database, and local access to the
|
|
managed Git repositories.
|
|
|
|
EXAMPLES
|
|
--------
|
|
To rescan all known trackingids:
|
|
|
|
====
|
|
$ java -jar gerrit.war ScanTrackingIds -d site_path --threads 16
|
|
====
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:index.html[Gerrit Code Review]
|