Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #28037

Closed (moved)
(moved)
Open
Created Oct 15, 2018 by teor@teor

Document how to fix or disable failing CI

We want our CI to always be passing.

Sometimes, we can fix the bug quickly, or revert the commit. But if the CI environment is broken, we need to disable the failing test cases until the bug is fixed.

In doc/HACKING, document how to disable failing CI jobs. In the Travis and Appveyor configs, summarise or give an example of how to disable a failing CI config.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking