report.sarif not generated

I’m running infersharp on Azure DevOps, using the example provided.

Here’s the snippet from my pipeline YAML:

  # Download binaries
  - task: DownloadBuildArtifacts@0
    displayName: 'Download binaries'
    inputs:
      buildType: 'current'
      downloadType: 'single'
      artifactName: 'infersharp-input'
      downloadPath: '$(System.ArtifactsDirectory)'

  - script: |
      curl -o run_infersharp.sh https://raw.githubusercontent.com/microsoft/infersharpaction/v1.4/run_infersharp_ci.sh
      chmod +x run_infersharp.sh
      ./run_infersharp.sh $(System.ArtifactsDirectory)
    displayName: 'Run Infer# analysis'
  # Display as build console logs
  - script: cat $(Build.SourcesDirectory)/infer-out/report.txt
    displayName: 'Infer# analysis result'
  
  - script: ls $(Build.SourcesDirectory)/infer-out
    displayName: 'list folder contents for debugging'

  # Publish SARIF
  # - task: PublishBuildArtifacts@1
  #   displayName: "Publish Infer# SARIF"
  #   inputs:
  #     PathtoPublish: "$(Build.SourcesDirectory)/infer-out/report.sarif"
  #     ArtifactName: "infersharp-output"
  #     publishLocation: "Container"

You can see I’ve commented out the publishing of the SARIF file, as it doesn’t seem to be present. Here’s the listing of the output folder after running infersharp:

bugs.txt capture.db capture.db-shm capture.db-wal config-impact-report.json costs-report.json logs report.json report.txt results.db results.db-shm results.db-wal tmp

Is report.sarif no longer generated by default?

[spaasis]

@xinshiMSFT thanks, that modification worked for us at least 👍

[jkuek]

Thanks for your help, I will close this issue now. (By the way, I don’t think .inferconfig needs to be executable and have put a comment to that effect in #197 )