Endevor Webhooks data placed in the Webhooks watch directory is formatted using a default format. Is there any way to parse the data in the webhooks watch directory before an action is triggered?
What's your end goal Phil? There is a PTF now available that will let you log to multiple directories, so you can now log actions into separate directories or log actions from different Systems or Environments separately using multiple ELEMENT LOGGING statements. See SO06259.
I'll be in touch Ed. I'm working with my internal customer and I'll provide more info. Thanks!
Say for example, I have a package action placed in the directory, if I can parse the package ID to Jenkins, then I can trigger the deploy process automatically, instead of waiting for user input (user to key in the package ID). So my end goal would be to trigger the process without manual intervention.
Ed, The package ID is stored in the webhooks watch directory. It appears that Jenkins is not picking up the package ID when triggering the Jenkins payload. Have you been able to trigger a Jenkins payload using the package ID from the webhooks watch directory? Thanks, Phil
So you need to install something like the 'Generic Webhook Plugin' on your Jenkins server if you've not already, that configures you an End Point to direct your Webhooks at. You then set up a Webhook via the Webhook configuration page (see "Configure a Mainframe Webhook" in the manual).
The Webhook server will then monitor your directory for log files and then consume these and post Webhooks out to your Jenkins server. You can then use the 'Generic Webhook Plugin' to consume these hooks on the Server as part of a Pipeline or Freestyle Project.
Thanks for the info Ed!