You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Some comments remain active in AzureDevops PR, although they are marked as closed in the sonar.
These issues are in sonar twice.
To Reproduce
Steps to reproduce the behavior:
I'm not entirely sure, but I'd say the problem occurs when the pipeline starts in AzureDevops, but before it finish, the programmer make a push with some SQ issues fixes. This cancels the running pipeline and starts a new one. After that the fixed issues are not closed in PR.
Create PR with issues
Sonnar will create comments in PR
Push commit to Azure
Azure trigger PR validation pipeline
Push commit to Azure with fix of some issues (maybe you have to wait until "Prepare Analysis Configuration" finish, but before "Run Code Analysis" task start.
Azure cancels pipeline from step 4 and trigger new one
Issue is closed in sonar but not in Azure
Expected behavior
I expect that corresponding thread in PR will be closed.
Screenshots
If applicable, add screenshots to help explain your problem.
Software Versions
SonarQube Version: 8.4.2.36762 in docker
Plugin Version: 1.5.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I tried to simulate the error again, but without success. So the problem still exists, but I don't know how to simulate it.
I'll leave the TRACE log enabled and when the problem reappears, I'll check the log and upload it here.
Describe the bug
Some comments remain active in AzureDevops PR, although they are marked as closed in the sonar.
These issues are in sonar twice.
To Reproduce
Steps to reproduce the behavior:
I'm not entirely sure, but I'd say the problem occurs when the pipeline starts in AzureDevops, but before it finish, the programmer make a push with some SQ issues fixes. This cancels the running pipeline and starts a new one. After that the fixed issues are not closed in PR.
Expected behavior
I expect that corresponding thread in PR will be closed.
Screenshots
If applicable, add screenshots to help explain your problem.
Software Versions
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: