anchor.diff:  
   ==== Output
   
  -After the job runs, you can view the results on the Job Details page in ElectricFlow. The procedure was completed successfully.
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildcleanup/ec-gerrit-devbuildcleanup3.png[image]
  -
  -In the *DevBuildCleanup* step, click the Log button to see the diagnostic information. The output is similar to the following diagnostic report:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildcleanup/ec-gerrit-devbuildcleanup4.png[image]
  +After the job runs, you can view the results on the *Job Details* page in {CD}. In the *DevBuildCleanup* step, click the *Log* button to see the diagnostic information.
   
   [[DevBuildPrepare]]
   
   
   === DevBuildPrepare
   
  -Developer builds are used to build a single patch set submitted by a developer. ElectricFlow scans Gerrit on a regular basis to find new patch sets to process. What the plugin does depends on the value you set for the *Developer Build Mode* in your plugin configuration.
  +Developer builds are used to build a single patch set submitted by a developer. {CD} scans Gerrit on a regular basis to find new patch sets to process. What the plugin does depends on the value you set for the *Developer Build Mode* in your plugin configuration.
   
   The DevBuildPrepare procedure prepares for a developer build. This will be one change. The working tree is adjusted to be the head of the branch and updated with the changes.
   
  
positive.code: 
  ==== Output
  
  After the job runs, you can view the results on the Job Details page in ElectricFlow. The procedure was completed successfully.
  
  image::cloudbees-common::cd-plugins/ec-gerrit/setupgerritserver/ec-gerrit-setupgerritserver3.png[image]
  
  In the *SetupGerritServer* step, click the Log button to see the diagnostic information. The output is similar to the following diagnostic report:
  
  image::cloudbees-common::cd-plugins/ec-gerrit/setupgerritserver/ec-gerrit-setupgerritserver4.png[image]
  
  [[TeamBuildCleanup]]
  
  
  === TeamBuildCleanup
  
  Team builds are designed for the build and release team. These builds combine changes of one or more patch sets to test how multiple changes will work together. The plugin finds patch sets based on rules provided in the _Team Build Rules_ property in the plugin configuration. The plugin does not run team builds automatically. You must run team build procedures from ElectricFlow.
  
  The TeamBuildCleanup procedure marks the changes as approved if the job is successful. It also reverts any uncommitted changes from the working directory.
  
  
negative.code: 
  . Add the repo tool to the PATH environment variable for the resource where the plugin will run. If the path cannot be updated for the resource, update the plugin property called _pseudo_code/repo_cmd_ to point to the repo tool. This plugin uses the repo tool for synchronizing with the Git repositories and downloading changes from the repositories.
  . Grant *Access Database* capability to the Gerrit user configured to communicate with the Gerrit server. Since Gerrit 2.6, Gerrit administrators no longer have the *Access Database* capability by default. This capability is required by the plugin for access to the Gerrit database using the *gsql* command.
  
  You perform these procedures in the {CD} UI.
  
  == Creating {CD} resources
  
  Create one or more resources where your builds will run. Group these resources in one or more pools. When you create the Gerrit plugin configuration later, you can specify a pool name for the resources to use.
  
  You can also set a special property called _gerrit_working_dir_ for each resource. The value of this property is the directory where you want to put build sources. This directory can be relative to the current directory (the standard {CD} workspace created for the build) or absolute.
  
  When the plugin runs, it checks if the directory exists. If the directory is found, {CD} assumes there is a repository and only synchronizes changes. If the directory is not found, the plugin creates one and does a full initialization and synchronization of the repository. Because this process can be time consuming, the plugin also supports using cached directories.
  
  You can setup one or more locations where builds can be run. Directory contents are not deleted after a build so the plugin only needs to reset and synchronize to the head of the branch at the start of each build. Assuming you build the same branch many times, each reset and synchronization will run much faster than a full initialization and synchronization. Changes are applied as before.
  
  This example shows how to create resource.
  
  . Go to the *Cloud* tab in the {CD} UI.
  
  You can create the resource using the Gerrit tool or edit an existing one:
  
  . Provide the parameters to create the resource.
  . Add the required _gerrit_working_dir_ property by clicking *Create Property* in the *Custom Resource Properties* section.
  . Provide the name of the property and the value.
  
  == Scheduling when the Gerrit server is scanned
  
  The plugin scans your Gerrit server for changes every 15 minutes. based on an {CD} schedule. If you want to change this frequency, modify the "Gerrit New Change Scanner" schedule in the *Administration* > *Plugins* > *EC-Gerrit* > *Schedules* page in {CD}.
  
  == Changing resources in procedures
  
  