Conversation

Notices

1. Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Thursday, 24-Feb-2022 14:09:26 UTC Santa Claes 🇸🇪🇭🇰🎅
   Been fighting SonarQube documentation so hard tonight. I finally won.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 25-Feb-2022 07:27:29 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to
     This is an "unfortunately I am now the authority on this" situation.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 25-Feb-2022 07:48:21 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to
     The solution is to record an #HPREp on the topic of sonar.properties (and -D parameters, same thing) and its mapping to the UI project settings and to docs.sonarqube.org/latest/proj… and then send anyone who asks to that episode and its shownotes.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 25-Feb-2022 07:50:20 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • glyn
     @underlap just made a note to do so =)
     
     libranet.de/display/0b6b25a8-6…
     
     The quick answer is that if you want to know the property for a setting, it is shown in the UI just below the input box for the setting. It's all just browsing and keeping an eye out from there.
   • glyn (underlap@fosstodon.org)'s status on Friday, 25-Feb-2022 07:50:21 UTC glyn

     in reply to

     @clacke Are you going to capture your findings somewhere?

   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 25-Feb-2022 11:15:11 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to
     The problem being that Sonar documentation is all about messing about in the UI. Seriously, who does that? I thought if you used Sonar you would generally be a company with 1000 devs and almost as many repos.
     
     Configuration needs to be visible and versioned.