Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • 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 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Packages
    • Packages
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issues
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #63303

Closed (moved)
Open
Opened Jun 16, 2019 by André Hänsel@AndreKR
  • Report abuse
  • New issue
Report abuse New issue

Auto-cancel redundant, running pipelines

Problem to solve

There is already an option "Auto-cancel redundant, pending pipelines". However, this cancels only pending jobs, not running jobs.

Some jobs, like frontend tests, can run for a long time (GitLab itself has pipelines running more than an hour), they take up resources and thus make other pipelines slower. If a new version of the same branch is pushed during that time, there is no use in finishing the pipeline for the old version. Running jobs should just be canceled to free up resources for the new pipeline.

Intended users

Developers, DevOps people

Proposal

Either change the option "Auto-cancel redundant, pending pipelines" to include already running jobs. This would be my preferred version, as I see no benefit in finishing outdated jobs. However, this might break someone else's workflow(?) so maybe it's better to add a second option "Cancel running jobs as well".

Edited Jun 16, 2019 by André Hänsel

Linked issues

  • Discussion
  • Designs
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-foss#63303