Backend: The protected env job showing the pipeline Creator name instead of Triggerer name on Gitlab UI
Summary
Protected env job showing the pipeline Creator name instead of Triggerer name on Gitlab UI
Steps to reproduce
This is a UI issue.
To trigger this behavior you need to have an environment setup (Prod) once you have your environment set protect the master
branch so that only Developers and Maintainers
can merge.
You will also need to protect the master branch with allow role
for Maintainer
on it only.
Once this is done have a Developer
create a new job on tag
that will eventually be merged into the master
branch and create a manual job that when triggered merges into the master branch.
Once the pipeline is executed and gets to the manual job that will push to master only the Maintainer
should be able to execute the job.
The job sometimes shows that the Maintainer
is the author
of the job, other times it shows that the Developer
is the author of the job.
Example Project
Refer to reference ticket for a detailed example on customer pipelines.
What is the current bug behavior?
The author of a job pushed to master is the Developer
What is the expected correct behavior?
The author of a job pushed to master is the Master
based on the protected master branch
Relevant logs and/or screenshots
Refer to reference ticket for a detailed example on customer pipelines.
Possible fixes
Additional technical notes
- The pipeline data is GraphQL and comes from
getPipelineQuery
- The job data is REST and the endpoint comes from
job_data
which is injected into the job app