title: How to use the three steps of Jenkins Warnings Next Generation Plugin properly?
body: <p>The Jenkins Warnings Next Generation Plugin's <a href="https://www.jenkins.io/doc/pipeline/steps/warnings-ng/" rel="noreferrer">documentation</a> for pipelines specifies three step variants:</p>
  
  <ul>
  <li><code>publishIssues</code>: Publish issues created by a static analysis scan</li>
  <li><code>recordIssues</code>: Record compiler warnings and static analysis results</li>
  <li><code>scanForIssues</code>: Scan files or the console log for warnings or issues</li>
  </ul>
  
  <p>I've just tried this simple snippet out:</p>
  
  <pre><code>stage('QA checks') {
      steps {
          recordIssues([
              enabledForFailure: true,
              tools: [php()]
          ])
      }
  }
  </code></pre>
  
  <p>and got the result displayed on the build's page ("PHP Runtime: No warnings"). But then what is the sense of the other two steps?</p>
  
  <p>What is a proper way of configuring the plugin? Should these three parts be used, like this?</p>
  
  <pre><code>stage('QA checks') {
      steps {
          scanForIssues([...])
          recordIssues([...])
          publishIssues([...])
      }
  }
  </code></pre>