Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • J Jenkins jobs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Infrastructure
  • CI CD
  • Jenkins jobs
  • Issues
  • #2066
Closed
Open
Issue created Nov 07, 2019 by Stefano Zacchiroli@zackMaintainer

when pushing several commits, only run CI on the most recent commit

As per title. It sounds like a waste of resources and leads to a lot of notification about pointless build failures when only the most recent commit pass CI. The current state of affairs might also discourage people from splitting work into multiple commits to avoid the notification storm, which is undesirable.


Migrated from T2066 (view on Phabricator)

Assignee
Assign to
Time tracking