Skip to content
Discussion options

You must be logged in to vote

Hi there! And thank you for trying out xyOps.

Ah, you've discovered a bug. I was failing to promote the job output data into the hook data which is used by actions. So sorry about that. A fix is coming ASAP.

Once the new build is out (should be tonight or tomorrow at the latest):

What you want to do is, inside your event plugin shell code, output some "data" for xyOps to pick up, like this:

echo '{ "xy":1, "data":{ "priority":"high" } }'

This will populate job.data which actions (including web hooks) can access. So then you can use macro placeholders in the web hook content body like this:

{{ job.data.priority }}

Thank you for reporting this!

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
2 replies
@webdb22
Comment options

@jhuckaby
Comment options

Answer selected by webdb22
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants