We’re having exactly the same problem here. It would be great if there were some improvements.
I can see the quality gate result in SonarCloud, but it is not reporting back to the PR in DevOps, thus the PR is stuck with the quality gate status check in “Waiting”.
I rotated the token, removed and re-added Quality gate status in the repo settings
This happend today randomly.
I have 5 repositories in my organization and the samme issue appears everywhere
In background tasks in sonar - all success, they pass but in devops is still waiting
Hi,
Welcome to the community and thanks for this report!
To make sure, you say this happens randomly across 5 different repos? Meaning that sometimes the quality gate status does get reflected back to ADO for, say, RepoA, and sometimes it doesn’t?
Thx,
Ann
We noticed the same in our PRs. Scan is working fine but PR decorations seems to be broken currently. We tried to change the PAT too and added some permissions which did not help.
Scan is working and as Mada B said - background tasks look normal
1 Like
Hi Ann,
It actually started today for all repos. we never had a problem until today
right now for all repos, the quality gate stays in waiting
to clarify what i meant - its not intermitent - so it does not sometimes happen sometimes not. until today everything worked fine.
now it stays in waiting for each repo
Same problem here
Feels like a v4.2.1 ADO SonarCloud extension issue
2 Likes
Hi Andy,
I cannot find a resolution.
I did check all posts regarding this even the one you showed me.
Anyone aware on how to fix this? It’s causing a lot of trouble.
There is no option to rollback to a previous version
Hi,
Apologies for the disruption, a release has just been issued to fix that.
2 Likes
Hi Claire.
Now i am facing a different problem
Every build i try to re-queue or run new i get this
i tried both self hosted agents and microsoft hosted
every build containing sonar tasks fails at the initialize step
Same here- I think this just got way worse
In the ADO pipeline “Initialize Job” step, right at the start, I see:
Downloading task: SonarCloudAnalyze (4.2.2)
Downloading task: SonarCloudPublish (4.2.2)
##[error]Offset to Central Directory cannot be held in an Int64.
1 Like
Hi there,
This is a different issue with Azure extension distribution, that is not on our control.
We are working with Azure at the moment - as described in this other thread, the workaround is to uninstall and reinstall the extension.
1 Like
Hi Claire,
But reinstalling the extension won’t cause any additional issues?
As mentioned. I have this issues on self hosted agents as well
For me it’s working again. (Pipeline + Policy)
For me same issue still.
Pipelines running in the small amount of time the extension is not installed will fail, that’s all.
Thank you for the reply.
Will there be an oficial fix that does not require a reinstall?
We are still working with Azure to find the root cause and any potential fix. We don’t have any information to communicate at this stage, I can just say our goal is to fix the issue without any intervention on our user’s side if it is possible.
1 Like
Thank you for your quick replies.
Hello. any updates?
Hi @Mada_B
Since the unzipping issue is unrelated to this thread, I’m not gonna give updates on this thread anymore about that issue. Please follow this other thread to get informed about any resolution when we’ll have one.
1 Like