Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
GLib
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 53
    • Merge Requests 53
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • GLib
  • Issues
  • #1767

Closed
Open
Created May 01, 2019 by Philip Withnall@pwithnallMaintainer

Fix scan-build reports and gate CI pipeline success on scan-build success

This is a follow-up from !563 (merged).

We need to squash all the scan-build reports, then add the following to .gitlab-ci.yml to gate pipeline success on there being no analysis reports:

variables:
  # Exit with a non-zero status if any bugs are found
  SCANBUILD: "scan-build --status-bugs"

This requires a Meson version bump to ≥ 0.49.0 to include the fix for https://github.com/mesonbuild/meson/issues/4334.

There’s an FAQ on the clang analyser which gives workarounds for common false positives: http://clang-analyzer.llvm.org/faq.html

Edited Sep 05, 2019 by Philip Withnall
Assignee
Assign to
2.69.0
Milestone
2.69.0
Assign milestone
Time tracking
None
Due date
None