Hello,
I upragde to Sonar 10.5.1 And uses Azure Devops plugin for analysis.
I’m just running a new build after updrage and new issues are created with an hour in the future : May 21,2024 at 4:11PM and my BUILD was at 2:51PM
Notification mail not showing issue because filtered to created at 14H51 :
&createdAt=2024-05-21T14%3A51%3A31%2B0200
What sould i do ?
Hi,
Check the server clocks on your build agent and SonarQube host.
HTH,
Ann
Hi,
server clocks seems to be ok (same hour and parameter than my PC)
Hi,
So the system clocks are both correct on the build agent and on the SonarQube host? What about on your DB?
Ann
Yes and it’s the same hour on my DB (SELECT Getdate() return the same hour than BUIDL and Sonar server).
Strange thing : i Have 2 planned triggers on my TFS BUILD :
2:00 => no problem
12:25 => problem
Hi,
To make sure I understand: Your analysis runs twice a day on the same infrastructure. One of those times, the dates come out fine and the other they come out an hour ahead?
Which implies that this happens reproducibly, every day?
Thx,
Ann
Yes, that’s it, it’s happen every day but only with build who run at 12:25, the same build at 2:00 works fine
Hi,
I don’t know what, but this is going to be something in your infra. SonarQube is pretty good about breaking consistently 
.
I’m sorry, but beyond the system datetimes, I don’t know where to tell you to look. Maybe start by talking to your infra folks to see what processes they have running around that time.
Ann
Hello,
After investigation, it seems that only rolsyn issues have this problem.
So I dont’ think that the issue is on my server side
