anchor.diff:  
   ==== Output
   
  -After the job runs, you can view the results on the Job Details page in ElectricFlow. Every job step was completed successfully.
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/custombuildprepare/ec-gerrit-custombuildprepare3.png[image]
  -
  -In the *CustomBuildPrepare* 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:* The step gets the list of changes to be processed and saves them for the rest of procedure. Because this procedure has no project parameter, the plugin search for changes in all the Gerrit projects, such as _ectest_ and _ECGerritTest_ projects:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/custombuildprepare/ec-gerrit-custombuildprepare4.png[image]
  -* *clone:* The step creates a clone of the remote repository:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/custombuildprepare/ec-gerrit-custombuildprepare5.png[image]
  -* *revert:* The step gets the tree in the clean state before overlaying files:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/custombuildprepare/ec-gerrit-custombuildprepare6.png[image]
  -* *apply:* The step gets the changes from Gerrit and overlays them on top of local repository:
  -
  -image::cloudbees-common::cd-plugins/ec-gerrit/custombuildprepare/ec-gerrit-custombuildprepare7.png[image]
  -
  -[[DevBuildCleanup]]
  +After the job runs, you can view the results on the *Job Details* page in {CD}. Every job step was completed successfully.
  +
  +In the *CustomBuildPrepare* step, click the *Log* button to see the diagnostic information.
  +
  +* *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:* The step gets the list of changes to be processed and saves them for the rest of procedure. Because this procedure has no project parameter, the plugin searches for changes in all the Gerrit projects.
  +* *clone:* The step creates a clone of the remote repository.
  +* *revert:* The step gets the tree in the clean state before overlaying files.
  +* *apply:* The step gets the changes from Gerrit and overlays them on top of local repository.
   
   
   === DevBuildCleanup
  
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/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]
  
  [[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.
  
  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.
  
  
negative.code: 
  ==== Output
  
  After the job runs, you can view the results on the Job Details page in {CD}. In the *DevBuildPrepare* step, click the *Log* button to see the diagnostic information.
  
  * *allocate:* This step checks that the required parameters in the configuration are correct. It has no output if the job was successful, and if an error occurs, the output shows the error details.
  * *annotate:* If this job was launched manually, annotate Gerrit so it knows about the job.
  * *clone:* The output shows that a clone of the remote repository was created.
  * *revert:* The output shows that the tree is put in the clean state before the files are overlaid.
  * *apply:* The output shows that changes are retrieved from Gerrit and overlaid on top of local repostory.
  
  === DeveloperScan
  
  