Rather than specifying a unique port for each job that uses ZAProxy, it would be ideal for the plugin to dynamically choose an available port. This could then be added to the build environment variables as ZAP_PORT for use by other build steps. Alternatively, the port field could support expansion of environment variables so that it could be set to something like 850${EXECUTOR_NUMBER}.