[NEW RELEASE] YAML Plugin 1.0.0


(Sbaudoin) #1

Hello everybody,

I have developed and released a SonarQube plugin to analyze YAML code:

To come: a extension plugin for Ansible playbooks.

Please, can you add the plugin in the Plugin Library page?


(G Ann Campbell) #2

Hi,

It doesn’t work quite like that. I can easily add you to the Other Plugins page if you like. But the Plugin Library page reflects the content of the Marketplace, and the requirements for that are slightly more stringent (in that there are requirements :smile:).

I haven’t looked your plugin over yet for compliance. Before I do, is that what you want?

Ann


(Sbaudoin) #3

Hello,

I was just following what’s described in the requirement page for deploying to the market place. As I tried to follow the market place’s requirements, I hope my plugin can integrate it, but in the meantime, or if you think the plugin is not eligible to the market place, please add it to the Other Plugins page.


(G Ann Campbell) #4

Hi,

I don’t know yet. I’ll take a look at this “soon” (hopefully tomorrow). :wink:

Ann


(G Ann Campbell) #5

Hi,

There are two points you might want to address, but they’re optional:

  • You’ve named it “SonarQube YAML Plugin”, which seems a bit redundant. “YAML Plugin” or “YAML Analyzer” might be better.

  • Also, the analysis log is a little chatty. I was only analyzing 4 files & got this:

    INFO: Reflections took 37 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 5 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 8 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 4 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 15 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 13 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 6 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 13 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 3 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 4 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 3 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 15 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 3 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values
    INFO: Reflections took 2 ms to scan 1 urls, producing 5 keys and 27 values

Other than that though, this looks great and I’ve added it to the Marketplace (and the Plugin Library page :wink:)

Ann


(Sbaudoin) #6

Thanks a lot.

I’m a bit annoyed with the numerous INFO traces. They come from a 3rd party library I use in a dependency and unfortunately I have not find a way yet to disable them. I cannot figure out how the Sonar scanner gets the log traces of this library. Can you help me, please?


(Sbaudoin) #7

OK, I managed to remove these annoying traces with a logback configuration. I’ve just released a new version 1.0.1 with a better name (“YAML Analyzer” as suggested) and the Reflections traces removed. Should I post a new release message in this forum?


(G Ann Campbell) #8

Hi,

To dot the 'i’s, yes please.

:slight_smile:
Ann