Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • 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 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #79619

Closed (moved)
Open
Opened Jan 14, 2021 by Marlon Regenhardt@Regenhardt0 of 6 tasks completed0/6 tasks

Filter pipelines by tags like latest

Release notes

Problem to solve

Have an overview about which branches currently fail CI and which ones do not.

Intended users

Delaney (Development Team Lead)
Wants to know the overall progress and status.

Sasha (Software Developer)
Wants to know how the others are doing.

Devon (DevOps Engineer)
Wants to know if there are unusually many pipelines failing, maybe due to system problems.

User experience goal

The user should be able to get a quick overview across all current branches without having to check which pipelines belong to the same branch and are outdated.

Proposal

Add a token to the filters on the pipelines page that allows the user to filter by pipeline tags like latest or scheduled.

Further details

There are currently sporadic problems with our gitlab runner. Fixing the runner means restarting all pipelines that failed due to that problem, which means looking at just the latest pipelines.

Permissions and Security

Same as other filters on the pipelines page.

Documentation

Availability & Testing

Available Tier

Free

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

Acceptance:

  • Pipelines can be filtered by tags latest and scheduled

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited Jan 14, 2021 by Marlon Regenhardt
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#79619