mattermost-plugin-gitlab icon indicating copy to clipboard operation
mattermost-plugin-gitlab copied to clipboard

Subscriptions don't work - subscribes fine but doesn't post anything after that?

Open CaerphillyMediaLtd opened this issue 4 years ago • 7 comments

We're using:

GitLab Community Edition 12.5.0 Mattermost Version 5.20. GitLab Plugin Version 1.1.0

I've set it up with an account just fine, have registered the application, etc. I invited the gitlab account to the team and channel. Then done:

/gitlab subscribe whatever-group/thisthat pushes,issues,issue_comments

Which is successful, if I enter an invalid repository then it errors, so it's definitely connected. But whenever a new push/issue/comment is made nothing happens. It just sits there and carries on like normal.

CaerphillyMediaLtd avatar Apr 01 '20 18:04 CaerphillyMediaLtd

@CaerphillyMediaLtd did you create and test a project hook in GitLab?

https://github.com/mattermost/mattermost-plugin-gitlab#step-3-create-a-gitlab-webhook

ericjaystevens avatar Apr 01 '20 20:04 ericjaystevens

I have exactly the same problem.

Gitlab Enterprise Edition 12.7.2-ee Mattermost version 5.21.0 Gitlab plugin version 1.1.0

I'm using a Group webhook (One webhook for all the subgroups and subprojects). When I use test the push tag event, the bot correctly notify about the tag in the channel.

When I tag one of my repo, its doesnt display anything in channel.

gvcgael avatar Apr 09 '20 09:04 gvcgael

After some deeper testing, this plugin is only compatible with project hooks, not group hooks.

gvcgael avatar Apr 10 '20 13:04 gvcgael

Follow up: Is there a release coming out for Gitlab that has Group Webhooks for non-ee edition?

aaronrothschild avatar Apr 14 '20 13:04 aaronrothschild

@CaerphillyMediaLtd @gvcgael if you are the author of the event you will not be notified. Is it the case?

iomodo avatar Apr 22 '20 18:04 iomodo

@CaerphillyMediaLtd let me know if this is still an issue. Just to add some info here for clarity:

  • It is possible to save a subscription without actually having a webhook in place to deliver the events. Make sure there is a webhook to deliver from the target protect
  • If the webhook was successfully created, you can test the webhook from GitLab side to collect more info

DHaussermann avatar Jan 26 '22 22:01 DHaussermann

Follow up: Is there a release coming out for Gitlab that has Group Webhooks for non-ee edition?

I think this is the reason why we are seeing the following when registering a webhook for a group project:

/gitlab webhook add grp-act/act-repo

POST https://gitlab.localdomain.com/api/v4/projects/3464/hooks: 422 {error: Invalid url given} (Only visible to you)

No webhook is visible on the project side.

unode avatar Sep 05 '23 17:09 unode