| 1 |
Hi all, |
| 2 |
|
| 3 |
Amongst Git migration preparations, one of the previously mentioned |
| 4 |
items was that GitHub's webhooks were very useful for many tasks. |
| 5 |
|
| 6 |
The QA team is already using them on the gentoo-portage-rsync-mirror |
| 7 |
repo, to trigger regular Travis-CI runs. |
| 8 |
|
| 9 |
In line with our policies of not depending on closed source and concerns |
| 10 |
about the persistence of GitHub, I've got an initial cut of WebHook |
| 11 |
support for Gitolite. These will probably be the primary means of |
| 12 |
interaction with external services, as we'd prefer not to give gitolite |
| 13 |
any SSH private keys to reach out to the world. |
| 14 |
|
| 15 |
It's based on the notify-webhook project [1], I also have the blessing |
| 16 |
of that author to improve his code and push generic changes to it. |
| 17 |
|
| 18 |
I'm looking for testers: |
| 19 |
Do you have a repo on gitolite AND would like pushes to trigger a |
| 20 |
webhook? |
| 21 |
|
| 22 |
If so, please file a bug for the public details. Additionally, if your |
| 23 |
hook has a username/password/secret token, please send me a GPG email |
| 24 |
with those details. |
| 25 |
|
| 26 |
Details needed: |
| 27 |
- repo path |
| 28 |
- webhook URL |
| 29 |
- webhook contenttype (json or url-encoded [default]) |
| 30 |
- webhook auth details if any (user, pass, realm, secret token) |
| 31 |
|
| 32 |
I do have plans to make it self-service later, but that will be a while |
| 33 |
coming. |
| 34 |
|
| 35 |
[1] https://github.com/metajack/notify-webhook |
| 36 |
|
| 37 |
-- |
| 38 |
Robin Hugh Johnson |
| 39 |
Gentoo Linux: Developer, Infrastructure Lead |
| 40 |
E-Mail : robbat2@g.o |
| 41 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
Archives