Adds Discord Notifications

[night]

This pull request adds the ability to send build status updates to Discord via webhooks.

The configuration format looks like the following:

notifications:
  discord:
    channels:
      - [webhook_id]:[webhook_token]
      - [webhook_id_2]:[webhook_token_2]
    pull_request_template:
      - 'Build [#%{build_number}](%{build_url}) ([%{commit}](%{compare_url})) of %{repository}@%{branch} in PR [#%{pull_request_number}](%{pull_request_url}) by %{author} %{result} in %{duration}'
    branch_template:
      - 'Build [#%{build_number}](%{build_url}) ([%{commit}](%{compare_url})) of %{repository}@%{branch} by %{author} %{result} in %{duration}'

Related PRs:
travis-ci/travis-core#562
travis-ci/travis-hub#84
travis-ci/docs-travis-ci-com#1133

[BanzaiMan]

Thanks for opening this PR. We'll get back to you soon.

[night]

any updates? soon might have been a misnomer, lol.

[Xstoudi]

Usefull PR ! 👍

[james7132]

Waiting warmly for this PR to be merged.

[night]

@BanzaiMan any feedback or updates?

[shirbr510]

Useful PR! +1 to @night !

[TobiTenno]

+1

[TobiTenno]

@BanzaiMan sorry for the ping, but any updates? it's been a while and this would be amazing to get working.

[night]

I doubt we'll ever get a reply to this, but I think they've already made up their minds and have settled on a "no" to this integration, but are too afraid to say it. I mainly did this for hacktoberfest swag anyways, so it doesn't really irk me. But it woulda been kinda cool to see this be integrated. ¯\_(ツ)_/¯

[TobiTenno]

have you seen any workarounds with existing integrations like their slack integration to force it to send to a webhook with slack structure? since they have similar structure, it's what i've done on sentry for some projects.

[durandj]

@night, would love to see this added! Maybe they haven't merged it because of a build failure here: travis-ci/travis-core#562

[TobiTenno]

The failure there is a dependency version issue, the dependency requires 2.1, bit it's trying to run against 2.0, @night. is that the only version of net-http-persistent that works?

[night]

@aliasfalse that test failing is not my fault nor my responsibility to fix, and there's already an open PR to fix the build, but it's unmerged as of November of last year.. the failing test is not a valid reason why this is not yet merged either.

[BanzaiMan]

Tasks should be core-less at this point.

[BanzaiMan]

Tested in staging (with my added logging and conflict resolution):

2017-02-20T02:53:02.282202+00:00 app[tasks.1]: I queue=discord notifier=discord build=542711 repo=BanzaiMan/travis_staging_test  time=0.001 jid=d2ecd4560a4c61671350ed84 event=push

If you want to test this now, please set up a repository on https://staging.travis-ci.org (go to https://staging/travis-ci.org/profile/USER; sync and enable a repo; push a commit to the repo).

[BanzaiMan]

Also, please open a documentation PR for https://github.com/travis-ci/docs-travis-ci-com.

[StarSmasher44]

Will be implemented when? @night @BanzaiMan Since this seems like a great feature.

[Stanzilla]

Yup, this would be awesome to have!

[DarthMDev]

+1

[BanzaiMan]

Hello. Sorry about the delay in responding. After some further internal discussion, we have put this PR on hold.

[Techtony96]

I figured I would add this here, I emailed support wondering if there was a way to send a slack webhook to a custom URL, rather than putting in the slack code and token, and this was the response I got (about 10 minutes before the reply above, from the same representative)

Hi, Tony,

Thanks for the email.

At the moment, it is not possible to pass URL to the Slack notifier, as the endpoint is hardcoded.

We have an outstanding PR #71 that implements support for Discord. As indicated there, however, we have unfortunately decided to put it on hold. You are welcome to subscribe to the PR for any future updates, though.

It might be possible to write a small service that takes our webhook payload and POSTs data to the discord endpoint after appropriate transformation.

Thank you.

[Techtony96]

Figured I would post this here as I took BanzaiMan's suggestion and made a small php script that forwards a travis-ci webhook on to discord. It looks like:

The repo is here: https://github.com/Techtony96/TravisCI-Webhooks/

[night]

I have created a PR for documentation at travis-ci/docs-travis-ci-com#1133, which should unblock this should I be a blocker.

[OwlManAtt]

Is there something we can do to unblock this, @BanzaiMan?

I too have a shim in place to transform your webhook format into my desired discord message, but that rather defeats the purpose of having all my CI infrastructure in the cloud :)

[Brodan]

@BanzaiMan any updates? I'm practically done with a PR to implement native Twilio support but I'm worried it's going to go untouched indefinitely.

[msgerbs]

I really don't understand why this has not been acted on or even meaningfully responded to in over a year.

[Jarvvski]

@msgerbs I too would like to know.

For now, I use the script written by @Techtony96 here

[Erlite]

Tbh it'd be awesome to have Discord support.

[Erlite]

For those of you that don't have a webserver for the php solution, I made a couple of scripts that run on the build server: https://github.com/Erlite/travis-ci-discord-webhooks

[TobiTenno]

So, why is it on hold? I don't think y'all are gaining anything and are in fact losing respect when you leave things like this open for several months with no reason why they're held back.

[Jarvvski]

@BanzaiMan Are we going to get any updates here? It would be helpful for the whole community if you shared your reasons for why this isn't being merged. That way, we can resolve that and move on

[iamtraction]

It's been more than a year, any updates yet?
In the meanwhile, for those who are still looking for a workaround, here's a simple guide to get Travis CI build status notifications via webhooks in Discord: https://github.com/k3rn31p4nic/travis-ci-discord-webhook
And you don't need any server for this.

Thanks @Erlite for the heads up.

[Arzte]

Asking for updates on a frequent basis is annoying and unhelpful, give the kind people at Travis some time to reply to the request for updates, a couple of days is not enough time for a response

[TobiTenno]

The submission date was October 2016, not 2017.

[Arzte]

Yes, but many have already @ mentioned or otherwise the people at travis already, any further attention seeking is annoying and uneeded.

[cryptiklemur]

Just trying to get answers @Coding-Doctors . Not really unneeded. Going over a year without an actual reason to why this hasn't been merged or even discussed is "annoying and unneeded".

After all, the squeeky wheel gets the grease.

[Arzte]

I was and have been referring to the past few days, not the entirety of the year+ this has been open.

[Celant]

Who knows, perhaps this will finally be merged, or at least a reason provided as to why not.

[AxisKriel]

👍

[Jarvvski]

LGTM