So far, indexing a series of changes had to be done by listing them one after the other which can be cumbersome when the number of changes to re-index is high. Add the possibility of indexing all the changes belonging to a project. Change-Id: Ib47f6d65ca49c85713d30806d7579f9d2d9cf823
		
			
				
	
	
		
			38 lines
		
	
	
		
			708 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			38 lines
		
	
	
		
			708 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
= gerrit index project
 | 
						|
 | 
						|
== NAME
 | 
						|
gerrit index project - Index all the changes in one or more projects.
 | 
						|
 | 
						|
== SYNOPSIS
 | 
						|
[verse]
 | 
						|
--
 | 
						|
_ssh_ -p <port> <host> _gerrit index project_ <PROJECT> [<PROJECT> ...]
 | 
						|
--
 | 
						|
 | 
						|
== DESCRIPTION
 | 
						|
Index all the changes in one or more projects.
 | 
						|
 | 
						|
== ACCESS
 | 
						|
Caller must have the 'Maintain Server' capability.
 | 
						|
 | 
						|
== SCRIPTING
 | 
						|
This command is intended to be used in scripts.
 | 
						|
 | 
						|
== OPTIONS
 | 
						|
<PROJECT>::
 | 
						|
    Required; name of the project to be indexed.
 | 
						|
 | 
						|
== EXAMPLES
 | 
						|
Index all changes in projects MyProject and NiceProject.
 | 
						|
 | 
						|
----
 | 
						|
    $ ssh -p 29418 user@review.example.com gerrit index project MyProject NiceProject
 | 
						|
----
 | 
						|
 | 
						|
GERRIT
 | 
						|
------
 | 
						|
Part of link:index.html[Gerrit Code Review]
 | 
						|
 | 
						|
SEARCHBOX
 | 
						|
---------
 |