I am looking for a way that a Guest in Project A could trigger a pipeline. I have looked into trigger tokens, project access tokens, and the CI_JOB_TOKEN but I can’t seem to figure out how to do this correctly. The use case is that for example someone outside of my team wants to run a pipeline to verify is the environment is up and running properly. They should not have developer access in this project, but I would like to know if there is a way that they could have Guest access and then I could grant them the ability to run a pipeline
Welcome to the forum @dsolomon!
As noted in the documentation only Developer and higher roles can run a pipeline.
Guests do have the ability to see the status of an environment for a project from the Environments screen.
I hope this helps!
-James H, GitLab Product Manager, Analyze:Product Analytics
1 Like
Thanks James. I also had this idea. Currently we’ve got this setup with 2 projects. Project A contains the BDD tests, and Project B contains trigger jobs to run the tests in Project A. Could we give people Developer permissions in Project B and Guest or Reporter permissions in Project A to view the results? And will they be able to trigger those tests given those permissions?
With multi-project pipelines the user triggering the pipeline in Project B needs to have permissions sufficient to trigger the pipeline in Project A, in your example, for it to work. So those users would still need at least Developer permissions in both projects.
-James H, GitLab Product Manager, Analyze:Product Analytics
2 Likes
Is there a way to give users only read access to a project and be able to still run a pipeline?