Skip to content
Open core software, built in Singapore Established 2018  /  Five utilities
Jering
Talk to us

Analyzers

DevOps.AzurePipelines Jering documentation Open source Pipeline templates
Documentation menu

Analyzers catch problems before they become release notes. A package pipeline should run them with the same settings a developer sees in the editor.

Why analyzers belong in the pipeline

An analyzer warning that appears only on a developer machine is easy to postpone. When the pipeline treats the same warning as part of the build, the team makes a deliberate decision: fix it or suppress it with a reason.

Setup

Enable the analyzer packages in the project and keep the rule set in source control. If a rule is suppressed, record why. The pipeline then runs the same rules as the local build.

Next

Read Packages In Depth for the metadata step that follows a clean build.

Reference shelf