Discord Integration for pipelines

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Discord notifications about Pipeline status don't work.

Steps to reproduce

  1. Enable Discord Integration.
  2. Tick the box "Pipeline - Event will be triggered when a pipeline status changes".
  3. Untick the box "Notify only broken pipelines".
  4. Cause a .gitlab-ci.yml trigger using a commit push.
  5. Get a notification about the commit.
  6. Get no notification when the pipeline completes.

What is the current bug behavior?

Pipeline notifications fail.

What is the expected correct behavior?

Get a notification about a completed pipeline.

Relevant logs and/or screenshots

sidekiq.log

ProjectServiceWorker JID-... ERROR: {:class=>"ProjectServiceWorker", :service_class=>"DiscordService", :message=>"400 Bad Request"}

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.5.3p105
Gem Version:    2.7.6
Bundler Version:1.16.6
Rake Version:   12.3.1
Redis Version:  3.2.12
Git Version:    2.18.1
Sidekiq Version:5.2.3
Go Version:     unknown


GitLab information
Version:        11.6.0
Revision:       075f960
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            ...
HTTP Clone URL: ...
SSH Clone URL:  ...
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:


GitLab Shell
Version:        8.4.3
Repository storage paths:
-default:      /var/opt/gitlab/git-data/repositories
Hooks:          /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 8.4.3 ? ... OK (8.4.3)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab App ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
7/1 ... yes
8/2 ... yes
9/3 ... yes
9/4 ... yes
9/5 ... yes
9/6 ... yes
9/7 ... yes
9/8 ... yes
9/9 ... yes
9/10 ... yes
9/12 ... yes
9/13 ... yes
9/14 ... yes
9/15 ... yes
9/16 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.5.3)
Git version >= 2.18.0 ? ... yes (2.18.1)
Git user has default SSH configuration? ... no
Active users: ... 6


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished
Edited by 🤖 GitLab Bot 🤖