webhook is a lightweight configurable tool written in Go, that allows you to easily create HTTP endpoints (hooks) on your server, which you can use to execute configured commands.
Does one of you have an example of hook definition for gitlab push?
I'm not sure how I'm supposed to use the rule
"type": "payload-hash-sha1" {
"match":
{
"type": "payload-hash-sha1",
"secret": "<SECRET>",
"parameter":
{
"source": "header",
"name": "X-Gitlab-Token"
}
}
}
So X-Gitlab-Token should be generated as the sha1 digest of the payload gitlab will send to the webhook, using the secret as the key
It ia used as security measure because someone who does not know the secret cannot generate the signature for the payload
If you configured gitlab to send your secret token in the header you will have to use match string rule instead :)
Hope this makes it a little bit clearer for you
If not, which application can?
Hey all, hoping for some pointers on what is likely a no-brainer. I'm getting the old
fork/exec /path/to/executable.sh: permission denied error. I have ensured that the file is indeed executable and the first line of my script contains #!/bin/sh. It's located in the home directory of the user under which I installed golang and webhooks. I'm setting this up on an AWS EC2 instance of the Linux AMI.
I'm successfully triggering the webhook, getting this error on attempted execution of the execute-command. I'm also running the
webhook command under the previously mentioned user account.
could you give us the output of the
ls -la /path/to/executable.sh command
maybe by accident you created the file as root, instead of the given user
which would result in the file being owned by the root user
also
try running the script manually as the given user
see if it will error on you
Hey @adnanh: Thanks for replying. I discovered that my
command-working-directory value was set to another user’s home folder, so that’s why permission was denied. Haha, pretty obvious in hindsight. Your suggestions led me straight to it, however so thank you. And thanks for webhooks!
@hrqiang try a classical web server like nginx?
bhook] 2017/01/14 16:21:07 os signal watcher ready
Jan 14 16:21:16 ubuntu webhooks[14938]: [webhook] 2017/01/14 16:21:16 bitbucket got matched
Jan 14 16:21:16 ubuntu webhooks[14938]: [webhook] 2017/01/14 16:21:16 error parsing JSON parameters: couldn't retrieve argument for {Source:payload Name:payload EnvName:}
Jan 14 16:21:16 ubuntu webhooks[14938]: [webhook] 2017/01/14 16:21:16 bitbucket got matched, but didn't get triggered because the trigger rules were not satisfied
Jan 14 16:21:16 ubuntu webhooks[14938]: [webhook] 2017/01/14 16:21:16 2017-01-14T16:21:16Z | 200 | 260.824762ms | prodeers.com:9999 | POST /hooks/bitbucket
Jan 14 16:21:57 ubuntu webhooks[14938]: [webhook] 2017/01/14 16:21:57 bitbucket got matched
error parsing JSON parameters: couldn't retrieve argument for
not able to match hooks
also
provide the hook definition you are using
My first hunch is that you are misusing configuration option, most likely a
parse-parameters-as-json?
@/all I have launched a SaaS version of webhook, if you'd like to check out the BETA, let me know. Find out more at www.hookdoo.com
if I wanted to pass the parameters to a command, for example, "--debug true" how can I do? Right now the parameters are passed to the command as json/dictionary? how can I make it to the form the command takes without a wrapper script?
Also, I see focus on build triggers, but how about other uses? You could easily imagine hookdoo as a gateway between web hooks and other services.
For example, monitoring provider A doesn't support alerting integration with, say Discord, but does provide a webhook alert. Enter hookboo gateway
