anchor.diff:        jenkinsfilePath: some/repo/dir/filename <1>
   ----
   
  -<1> An optional path within the repository that specifies the file to be used as the Jenkinsfile.  This path is relative to the 
  +<1> An optional path within the repository that specifies the file to be used as the Jenkinsfile.  This path is relative to the
   source `*contextDir*`, if any.  If left empty, the file must reside in the root of the repository or `*contextDir*`.
   ====
   
  
positive.code:   allowEnv: true <1>
  ----
  
  <1> Set to `*true*` to allow a generic webhook to pass in environment variables.
  ====
  
  To set up the caller, supply the calling system with the URL of the generic
  
negative.code: trigger on your `*BuildConfig*` and trigger it via your Gogs server also.
  ====
  
  Given a file containing a valid JSON payload, you can manually trigger the
  webhook via `curl`:
  
  ----
  $ curl -H "X-GitHub-Event: push" -H "Content-Type: application/json" -k -X POST --data-binary @github_payload_file.json https://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/github
  ----
  
  The `-k` argument is only necessary if your API server does not have a properly
  signed certificate.
  
  *Generic Webhooks*
  
  Generic webhooks are invoked from any system capable of making a web request.
  As with a GitHub webhook, you must specify a *secret*, which will be part of
  the URL that the caller must use to trigger the build. The secret ensures the
  uniqueness of the URL, preventing others from triggering the build. The
  following is an example trigger definition YAML within the `*BuildConfig*`:
  
  