Chatops does not work on gitlab.com
Summary
I'm unable to get chatops working with slack on gitlab.com .
The slack application is able to show issue content, but the run command does not work, it always displays Sorry, this chat service is currently not supported by GitLab ChatOps.
.
The ci job is however correctly started and seems to be given the expected $CHAT_INPUT
.
I initially brought this up in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24780#note_153165783 cc @proglottis .
Steps to reproduce
- Use gitlab.com
- Create public repository with shared runners
- Add a chatops ci job
- Configure the
Slack application
integration on the repository - Enter
/gitlab <repository> run echo hello
in slack
Example Project
https://gitlab.com/adrienbrault/chatops-test/blob/master/.gitlab-ci.yml
What is the current bug behavior?
The gitlab slack application displays Sorry, this chat service is currently not supported by GitLab ChatOps.
in chat after posting /gitlab <repository> run echo hello
.
What is the expected correct behavior?
I'm actually unsure about the exact behavior, but the slack application should tell me the job has has started/is done, and probably show the output.
Relevant logs and/or screenshots
https://gitlab.com/adrienbrault/chatops-test/-/jobs/183563545
Running with gitlab-runner 11.9.0-rc2 (227934c0)
on docker-auto-scale fa6cab46
Using Docker executor with image ruby:2.5 ...
Pulling docker image ruby:2.5 ...
Using docker image sha256:97f68e8fccc290fadf7634c95797892c54bdfd7bd0a0c2e8e4ea876b75802914 for ruby:2.5 ...
Running on runner-fa6cab46-project-11489032-concurrent-0 via runner-fa6cab46-srm-1553515216-47998fae...
Initialized empty Git repository in /builds/adrienbrault/chatops-test/.git/
Fetching changes...
Created fresh repository.
From https://gitlab.com/adrienbrault/chatops-test
* [new branch] master -> origin/master
Checking out 34180839 as master...
Skipping Git submodules setup
$ echo "Your input was: $CHAT_INPUT"
Your input was: hello
Job succeeded
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
This bug happens on GitLab.com
Results of GitLab application Check
This bug happens on GitLab.com
Possible fixes
No idea