Would like to be able to run entire pipeline through ChatOps, not just a single job
Problem to solve
Currently when using ChatOps we can only run a single job, which for me (and I suspect others) isn't very useful since all of our CI scripts are intended to be run as a complete pipeline.
This would be very helpful during a chat session to be able to kick off the entire pipeline and report the results back to the channel especially when troubleshooting issues with a build. Running a single job often doesn't provide much value in the context of a pipeline that contains build, test, validate, and deploy stages.
I would like to have a new slash command option like: /(trigger word) run pipeline or just /(trigger word) run-pipeline
Permissions and Security
The same permissions that allow a user to run slash commands today would apply to this as well. Users could exclude certain jobs from being run in chat in the gitlab-ci.yml file if they wish.
This wouldn't introduce additional risk as far as I can see since this wouldn't be granting a new permission that doesn't already exist.
What does success look like, and how can we measure that?
Success would be having a complete pipeline run successfully through ChatOps and receiving a notification attesting to that fact.
What is the type of buyer?
Premium and Ultimate