如何让GitLab CI中的ReSharper InspectCode任务在出现警告或错误时失败？

The issue you're hitting is that by default, the jb inspectcode command returns a successful exit code (0) even when it detects code issues—that’s why your GitLab CI job keeps passing regardless of warnings or errors. To make the job fail when problems are found, you need to add specific flags that tell InspectCode to return a non-zero exit code when issues of a certain severity are detected.

Here's how to update your .gitlab-ci.yml configuration to achieve this:

inspect:
  stage: inspectcode
  script: 
    - "jb inspectcode MySln.sln -o=report.xml --fail-severity=WARNING"
  artifacts:
    paths:
      - report.xml

Key Details About the Flag: #

• --fail-severity=WARNING: This flag tells InspectCode to fail (return a non-zero exit code) if it finds any issues with severity WARNING or higher (including ERROR-level problems). This ensures both warnings and errors will trigger a CI job failure.
• If you only want the job to fail on ERROR-level issues (and ignore warnings), replace the flag with --fail-severity=ERROR.
• You can also use the shorthand --fail-on-warnings as an alternative to --fail-severity=WARNING—they function identically.

Optional: Fine-Tune with a Custom Inspection Profile #

If you need tighter control over which specific rules should block the pipeline, you can create a custom ReSharper inspection profile (saved as a .DotSettings file) and reference it with the --profile flag:

inspect:
  stage: inspectcode
  script: 
    - "jb inspectcode MySln.sln -o=report.xml --fail-severity=WARNING --profile=MyCustomRules.DotSettings"
  artifacts:
    paths:
      - report.xml

This lets you enforce exactly which code quality standards are critical enough to stop your CI pipeline.

内容的提问来源于stack exchange，提问作者Nikita Burmistrov