News for hackers. Stuff that matters.

A comment on Sonar is destroying my job and it's driving me to despair. Parent comment

Re:Sonar is destroying my job and it's driving me to despair by ars on Tuesday July 02, 2024 @06:04PM (#40860857)
I use Sonar all the time, but not during build. It runs live while I'm editing a file. I've not noticed any slowdown at all, and it's certainly a quick feedback loop (it runs when I save the file).

I've found the majority of its suggestions helpful, and the ones that are not I simply ignore.

[ Parent | on HN ]
Re:Sonar is destroying my job and it's driving me to despair by nsxwolf on Tuesday July 02, 2024 @06:52PM (#40861209)
It adds about 2 minutes to our gitlab pipelines but the major issue with it is when organizations decide failures should prevent merging code to master or even deploying to a QA environment.

That's the real time sink - figuring out how to get past it. It's a lot more than 2 minutes, sometimes even days if it's something you can't work around and have to go through the red tape if your team isn't empowered to take charge of your own pipelines.

[ Parent | on HN ]
Re:Sonar is destroying my job and it's driving me to despair by raiyni on Tuesday July 02, 2024 @11:50PM (#40862577)
You think 2 minutes is bad, try using fortify. Scans can easily be hours.
[ Parent | on HN ]
Re:Sonar is destroying my job and it's driving me to despair by Emigre_ on Wednesday July 03, 2024 @02:45PM (#40868877)
I should have mentioned that I was referring actually to the continuous integration pipeline, not actually to the build itself. Not very well explained on my side. I've never used it locally myself. I don't really know why the CI setups that were using Sonar I've seen in the past were that slow, to be honest.
[ Parent | on HN ]