Azure DevOps Extension (v3) failing (System.IO.FileLoadException)

SonarQube Cloud
, ,
21

We are getting the error

##[error]System.IO.FileLoadException: Could not load file or assembly ‘SonarScanner.MSBuild.PreProcessor, Version=6.2.0.0, Culture=neutral, PublicKeyToken=c5b62af9de6d7244’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

In every build suddenly.

Statuspage says all is up but it’s hard to see that this is something on our end.

Are we alone in httting this?

Running in AzureDevops pipelines that have not been edited recently; using the SonarCloudPrepare@2 task.

22

This seems to be an issue with the sonar-scanner-azdo release that went out this morning. Also impacting us, and we are on a self-hosted SonarQube instance.

Unable to open a Github issue with that repo specifically unfortunately.

23

The workaround to force the version 6.3.2 worked for me, but I have too many repos to manually fix this in all of them.

Is there any ETA for a proper fix?

1 Like
24

Any possible workarounds for classic pipelines? Unfortunately not all our pipelines are on YAML yet.

25

Strange that theres no mention to 6.3.3 in installed version.

image
image1637×1429 149 KB

And how I’m using a version that’s not in the history of installed versions?

image
image598×336 58.1 KB

26

Try using version 5.

27

I am seeing this same thing. 7.0.0 installed in extensions, but the task is using 6.3.3

28

A simple workaround for now: just pin the older version in pipeline definition, like SonarQubePrepare@6.3.2 and all other sonar tasks you use., e.g.

  • task: SonarQubePrepare@6.3.2
    inputs:
    …
3 Likes
29

Same issue here

30

Same issue here. Why is it we have this situation so often where a new version of the task is pushed and breaks everyone?

1 Like
31

Same issue here, Is there any ETA??

1 Like
32

Hello,

We are also currently blocked by this using the @7 tasks.

- task: SonarQubePrepare@7
   displayName: SonarQube - Prepare
   inputs:
     SonarQube: "$(SonarEndpoint)"
     scannerMode: "dotnet"
...

image
image1329×453 26.1 KB

33

That works. Thanks! Make sure to downgrade all SonarQube tasks to that version, otherwise you’ll end up with a “missing variables…” error.

2 Likes
34

Hi all,

We’ve identified the issue, and are working on the fix. In the meantime, you can work around this by pinning to an older version.

 
Ann

2 Likes
35

I am using SonarCloud extension in AzureDevOps. I updated task version to 2.3.2 and it is working fine.
Is this the stable versions now?
How long can I live with it?
Is there a way to get communications when new task versions are available for SonarCloud?

36

Hello Ann,

Is there any workaround for builds defined with classic UI?

Ali

37

How do you update task to version 2.3.2?

38

In the yaml file I declared task version like

  • task: SonarCloudPrepare@2.3.2
3 Likes
39

Thanks, that worked for me. I was somehow convinced that dots are not allowed after @ sign :slight_smile:

40 
  - task: SonarCloudPrepare@3
    inputs:
      SonarCloud: 'xxxx'
      organization: 'xxxx'
      scannerMode: 'dotnet'
      dotnetScannerVersion: '6.2.0.85879'
      projectKey: 'xxxx'
      projectName: 'xxxx'

setting dotnetscanner version with specific version solved it for me, as a temp solution
refer to versions: