Pipeline Graph for external jobs
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
When building using external CI tools, like Jenkins, the pipeline graph only has one stage. Even if stages were created in a .gitlab-ci.yml file or on Jenkins itself, it keeps returning them as External:
Intended users
Intended users to benefit:
- Developers (On commit builds)
- DevOps Engineers (Overview of steps on project based pipelines)
- Project Manager (Sees steps taken per project at a glance)
Further details
Use cases:
- When current pipelines have been built on a platform like Jenkins, it is difficult to convince Managers and older developers to find their build statuses elsewhere
- Support multi-product deployments
Proposal
Currently there is a plugin for Jenkins - GitLab integration which allows the build steps to be executed to an external CI server. Possible solutions will be to set the stage names for each stage, if applicable, and assign the steps to those stages.
Then using the same method as the .gitlab-ci.yml file, outline the pipeline and create the pipeline graph to show the stages and steps in each stage.
Permissions and Security
Everyone as the build logs should be protected by the external CI tools
Documentation
Testing
What does success look like, and how can we measure that?
Having the same pipeline graph as shown by the .gitlab-ci.yml builds
What is the type of buyer?
Honestly, every package using the pipeline feature