Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,802
    • Issues 35,802
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,283
    • Merge Requests 1,283
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #232946

Closed (promoted)
Open
Opened Jul 30, 2020 by Jason Yavorska@jyavorska💬Contributor0 of 6 tasks completed0/6 tasks

Show DAG relationships in the pipeline view

Problem to solve

Allow users to track the progress of their jobs (explore adding tracker/message) and understand dependencies easily when using the pipeline view. This could be achieved by bringing in some capabilities from the DAG view.

Intended users

  • Sasha (Software Developer)
  • Devon (DevOps Engineer)
  • Simone (Software Engineer in Test)
  • Allison (Application Ops)

User experience goal

Improve DAG experience based on feedback gathered from the beta in the issue #220368 (closed).

Proposal

  • The When needs is used, the default view for the pipeline visualization would be based 'Organized by needs' (or DAG). But users would still have the option to toggle back to 'Organize by Stage' view
  • In the absence of 'needs' the default view would be 'Organize by stage' and the option to toggle would not be available
  • The connections between the jobs would always persist, in a non-overwhelming way. While hovering over a job, the train of jobs that depends on it would be highlighted along with the connection between them

Trigger_screen DAG_view2

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Insights

  • Show the status of the jobs along with the dependencies
  • Also show job that are not dependent on other jobs in the DAG visualization
  • Bring DAG capabilities into the existing pipeline visualization
Edited Sep 18, 2020 by Jason Yavorska
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#232946