Skip to content

Resolving Development Environment Issues

Jump to bottom
Simon Bennetts edited this page Nov 13, 2018 · 3 revisions

The build route we're using is pretty new and we haven't yet ironed out all of the problems. This page details things that may help resolve problems.

  1. Stop all ZAP instances. Check that there really are no ZAP instances running:
    • ps -ef | grep ZAP
    • ps -ef | grep Zap
  2. Kill any instances of webdrivers that are still running:
    • killall geckodriver
    • killall chromedriver
  3. Delete the hud-alpha-1.zap file from
    • ~/.ZAP_D/plugin
    • zaproxy/src/plugin
  4. Start the ZAP Desktop, make sure the HUD is NOT present
    • If it is then you're picking up another HUD file
  5. 'Check for Updates' in ZAP and install all of the add-ons that have updates
  6. Stop the ZAP Desktop
  7. Make sure the HUD repo is up-to-date with the branch you want to use
  8. Build the HUD using:
    • ./gradlew build deployZapAddOn
  9. Run the HUD regression tests using:
    • ./gradlew --continue check zapDownload zapRunTests
    • If they don't pass then further investigations will be needed
  10. If running ZAP via an IDE refresh the zaproxy/src/plugin directory in your IDE
  11. Start the ZAP Desktop
    • The HUD should now be present and at the right version
    • If there are any problems look for errors or warnings in the ~/.ZAP_D/zap.log files

Note that the HUD parameters are persisted in ~/.ZAP_D/plugin/config.xml. This is a text file - you can search for 'hud' and delete all of the HUD XML elements as long as you don't break the XML. You should only edit this while ZAP is stopped.

Clone this wiki locally