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/devbuildexample/ec-gerrit-devbuildexample3.png[image]
  -
  -In the *DevBuildExample* step, click the Log button to see the diagnostic information. The output is similar to the following diagnostic report:
  +After the job runs, you can view the results on the Job Details page in {CD}. In the *DevBuildExample* step, click the *Log* button to see the diagnostic information. The output is similar to the following diagnostic report:
   
   *GetCodeFromGerrit:* This step of the example runs the DevBuildPrepare procedure to take the selected change in the parameters and download a copy to work with it:
  -
  -* *allocate:* This step checks that the required parameters in the configuration are correct. It has no output if the job is successful. If an error occurs, it shows the error details.
  -* *annotate:* If this job was launched manually, annotate Gerrit so it knows about the job:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildexample/ec-gerrit-devbuildexample4.png[image]
  -* *clone:* This creates a clone of the remote repository:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildexample/ec-gerrit-devbuildexample5.png[image]
  -* *revert:* This gets the tree in the clean state before overlaying files:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildexample/ec-gerrit-devbuildexample6.png[image]
  -* *apply:* This gets the changes from Gerrit and overlays them on top of local repostory:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildexample/ec-gerrit-devbuildexample7.png[image]
  -
  -*DoWork:* This step does the build and test procedures. In this example, the job only prints a message:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildexample/ec-gerrit-devbuildexample8.png[image]
  -
  +* *allocate:* This step checks that the required parameters in the configuration are correct. It has no output if the job is successful. If an error occurs, it shows the error details.
  +* *annotate:* If this job was launched manually, annotate Gerrit so it knows about the job.
  +* *clone:* This creates a clone of the remote repository.
  +* *revert:* This gets the tree in the clean state before overlaying files.
  +* *apply:* This gets the changes from Gerrit and overlays them on top of local repostory.
  +*DoWork:* This step does the build and test procedures.
   **GerritCleanup:**This step cleans up the Gerrit environment, uploading the changes if the DoWork step is successfully completed or rejecting the change if the step fails:
  -
  -* *annotate:* This step approves or rejects the change and adds a comment to the change in Gerrit:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/devbuildexample/ec-gerrit-devbuildexample9.png[image]
  +* *annotate:* This step approves or rejects the change and adds a comment to the change in Gerrit.
   
   === TeamBuildExample
   
  
positive.code: === EC-Gerrit 2.1.0
  
  * Added support for Gerrit 2.8.5.
  * Updated the plugin logic to support the Gerrit review labels called _Code-Review_ and _Verified_. Starting with Gerrit 2.6, the Verified label is no longer installed by default. Follow the steps link:#gerrit-verified-label[here] to install the label that can be used with ElectricFlow.
  * Updated the plugin logic to handle user names specified in build rule filters.
  * Allowed the _Repository Server_ configuration parameter to optionally accept the protocol it uses for data transfer as part of the parameter value. The _Repository Server_ value can now be set as _ssh://my_gerrit_server.my_domain.com_ if _my_gerrit_server.my_domain.com_ is using Secure Shell (SSH). To maintain backward-compatibility, if the value is specified without any protocol as _my_gerrit_server.my_domain.com_, _Git_ is assumed to be the protocol by default.
  * Deprecated the SetupGerritServer procedure. This procedure is no longer supported in Gerrit 2.6 and later. Follow the steps link:#gerrit-setup[here] to configure Gerrit to work with ElectricFlow.
  * Added a _revert_ step to the DevBuildCleanup and TeamBuildCleanup procedures to revert any uncommitted changes from the working directory as part of the cleanup.
  * Added postProcessors to track the progress of the plugin procedures.
  
  
negative.code: 
  ==== Output
  
  After the job runs, you can view the results on the Job Details page in {CD}. Every job step was completed successfully.
  
  In the *TeamBuildPrepare* step, click the Log button to see the diagnostic information. The output is similar to the following diagnostic report:
  
  * *allocate:* This step checks that the required parameters in the configuration are correct. It has no output if the job is successful. If an error occurs, it shows the error details.
  * *changes:* This step gets the list of changes to be processed and saves for rest of procedure.
  * *annotate:* The step gets the list of changes to be processed and saves for rest of procedure.
  * *clone:* If needed, the step clones the remote repository in Gerrit to a working directory and then gets the contents. The tree should now be synchronized with the head of the master.
  * *revert:* The step gets the tree in the clean state before overlaying files.
  * *apply:* The step gets the changes from Gerrit and overlays on top of local repository.
  
  == Examples and use cases
  
  This plugin has preconfigured example procedures that include the basic process to do the following:
  