3 ms·
That is also the impression we got when we tried Mattermost. It came as a big surprise because we are using a selfhosted Gitlab instance and Mattermost is suppo
by eis 5y ago
That is also the impression we got when we tried Mattermost. It came as a big surprise because we are using a selfhosted Gitlab instance and Mattermost is supposed to have great integration with Gitlab but it really didn't work well. Maybe it is due to us having set up Gitlab within Docker, I don't know. In the end we got it working but it still didn't recognize a user from Gitlab. It really felt like they had some good start and ideas but then something changed and came to a halt.
- it33 5y agoMattermost CEO here, thanks for the mention and the feedback! Just curious, have you enabled the GitLab-Mattermost plugin? https://github.com/mattermost/mattermost-plugin-gitlab#configuration https://github.com/mattermost/mattermost-plugin-gitlab#confi... If it wasn't easy to find, that's on us, and we need to do a better job in making things more discoverable.
- Eremotherium 5y agoThe bundled Mattermost was a bit flaky IIRC but with a separate instance (in Docker) using Gitlab SSO was no problem. Using SSO for Sentry was a bit more problematic as it's an unofficial plugin but IIRC it was due to Gitlab not sending the correct scope.