which versions are you using: SonarQube 10.2.1, DevOps Plugin 5.17.2
how is SonarQube deployed: zip
After upgrading from (I think) 9.9 to 10.2.1, we do see a strange issue with one specific project. We have a lot of projects from different Azure DevOps Organizations and Projects, on-prem DevOps same as Cloud DevOps, but the issue only happens to ONE single On-Prem Devops project, but in this project to every repository/pipeline.
Other projects in the same DevOps Organization work correctly, using the same SonarQube DevOPs Plugin.
We only updated our SonarQube Server Instance, did not change the DevOps Plugin version.
After the update, all analysis for this one project are missing information about branches and PRs, hence, the PR Quality Gate status stays at “waiting” blocking all PRs. This looks a lot like Azure DevOps Quality Gate not decorating pull requests however, that was SonarCloud. We use on-prem SonarQube Server.
Looking at the background tasks for this project before and after the update the reason is visible there:
SonarQube no longer seems to know those are PRs or branches. The Scanner Context for the new analysis misses all information regarding Branch and PR. However, we did not change anything on DevOps side. Its clearly related to the SonarQube Server update, between working and not working Background tasks, we see the Project Reload Tasks triggered by the update.
Any idea what could cause this? I can not find anything relevant in the build logs yet.
Additionally, not sure if this is related:
For the same project, since the update, I got a few Background Task failing messages. This only happens for some single tasks, and tasks after these errors do not show the error but still are showing above issue.
The error about the failing task:
Error Details
Validation of project failed: o Date of analysis cannot be older than the date of the last known analysis on this project. Value: “2023-11-06T16:11:04-0800”. Latest analysis: “2023-11-06T16:11:21-0800”. It’s only possible to rebuild the past in a chronological order.
Again, nothing changed on DevOps side and this is the only affected project by this error as well, and started after the Server update.
Hi @denis.troller
you are totally correct. This project was still running @4 task versions and after updating to @5 it seems to be working again. Seems like the SonarQube Update broke compatibility with @4 tasks.
Thanks a lot for the quick resolution!
Greetings
