Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • See what's new at GitLab
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 5
    • Merge Requests 5
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #18141

Closed
Open
Opened Jun 02, 2016 by Mark Pundsack@markpundsackContributor0 of 1 task completed0/1 task

Add pipeline graph

Description

When looking at a pipeline, we currently render its builds as a list. This is fine for some use cases, but inadequate for others. We should render builds in a graph showing their sequential and parallel natures. A good solution would not take up an inordinate amount of vertical space and would add value by helping a user visualize the pipeline flow, and quickly identify problems in pipeline runs.

Proposal

Pipeline:

Add a pipeline graph above the existing build list. Show both. Possibly let the user collapse the pipeline graph if it's too large.

Todo

  • Collapsing parallel builds of similar name is not handled today. Ideally, we'd leverage automatically parallelized tests (#3819 (closed)), but we could define a convention for naming, such as job-name {index} {total} and interpret that as a collapsable, parallel job.

Links / references

  • Builds on #18516 (closed).
  • Continuation from https://gitlab.com/gitlab-org/gitlab-ce/issues/7141#note_12229433.
  • Jenkins Blue Ocean UI announcement.
Assignee
Assign to
8.11
Milestone
8.11 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#18141