My first sonar-compliance plugin contribution

36 views
Skip to first unread message

Ramesh Dara

unread,
Feb 25, 2015, 1:30:53 PM2/25/15
to jenkin...@googlegroups.com
Hi,


This is Ramesh Dara and its my first contribution to jenkins plugin. Following are the details as suggested.

GitHub plugin name: sonar-compliance
Personal GitHub ID : rdara
The existing GitHub repository to fork: https://github.com/rdara/sonar_compliance

Appreciate helping me getting started with my first plugin.

-Ramesh Dara

Ramesh Dara

unread,
Feb 26, 2015, 10:32:14 AM2/26/15
to jenkin...@googlegroups.com
Appreciate helping me to commit my plugin code.

-Ramesh Dara

Christopher Orr

unread,
Feb 26, 2015, 1:49:58 PM2/26/15
to jenkin...@googlegroups.com
Can you explain a bit more about what it actually does?
Is it similar at all to the existing Sonar plugin / could functionality
be added to that?

Also, it looks like you need to remove the global.jelly and index.jelly
files in the repo which seem to be copies of the sample plugin project.

-Chris
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/74eb0fa0-282b-4d18-9930-14eabeaecbbd%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/74eb0fa0-282b-4d18-9930-14eabeaecbbd%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

Ramesh Dara

unread,
Feb 26, 2015, 2:26:27 PM2/26/15
to jenkin...@googlegroups.com
Hi Chris,


Thanks for responding.

The purpose of the sonar plugin is to collect the metrics of a project. The purpose of this plugin is compliance.

The customer can chose static compliance (Similar to the sonar's emerging quality gate) or differential. The static compliance ensures the customer rule like "blocker_violations < 10".

The "differential" is the new concept, where the "difference of metrics" will be taken into consideration. This will ensure that "the new incoming code" will be as good as "target"ed code quality. 

By using this concept, I managed to get the code coverage from approximately 23% on 10000 lines with 4 founder members to 83% on 66000 lines with 30 member team in 1 year! No sonar compliance, no commit!

I want to contribute the concept and code to the open source community and its my first step.

I left global.jelly from the sample, as I may require to have it to deal with configuring sonar globally with security (api access keys).  

Thanks,
Ramesh Dara




On Thu, Feb 26, 2015 at 10:49 AM, Christopher Orr <ch...@orr.me.uk> wrote:
Can you explain a bit more about what it actually does?
Is it similar at all to the existing Sonar plugin / could functionality be added to that?

Also, it looks like you need to remove the global.jelly and index.jelly files in the repo which seem to be copies of the sample plugin project.

-Chris


On 26/02/15 07:32, Ramesh Dara wrote:
Appreciate helping me to commit my plugin code.

-Ramesh Dara

On Wednesday, February 25, 2015 at 10:30:53 AM UTC-8, Ramesh Dara wrote:

    Hi,


    This is Ramesh Dara and its my first contribution to jenkins plugin.
    Following are the details as suggested.

    GitHub plugin name: sonar-compliance
    Personal GitHub ID : rdara
    The existing GitHub repository to fork:
    https://github.com/rdara/sonar_compliance
    <https://github.com/rdara/sonar_compliance>

    Appreciate helping me getting started with my first plugin.

    -Ramesh Dara

--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-dev+unsubscribe@googlegroups.com
 <mailto:jenkinsci-dev+unsub...@googlegroups.com>.

To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/74eb0fa0-282b-4d18-9930-14eabeaecbbd%40googlegroups.com
 <https://groups.google.com/d/msgid/jenkinsci-dev/74eb0fa0-282b-4d18-9930-14eabeaecbbd%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/54EF6ACA.4090408%40orr.me.uk.

Kanstantsin Shautsou

unread,
Mar 3, 2015, 9:31:33 AM3/3/15
to jenkin...@googlegroups.com
Have you tried to request this feature with the sonar-plugin developers?
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

Ramesh Dara

unread,
Mar 3, 2015, 12:58:57 PM3/3/15
to jenkin...@googlegroups.com
Hi Kanstantsin,

Thinking of Lego blocks design, the sonar and the compliance are 2 different blocks. The sonar compliance will not restrict the user how he chose to collect the sonar metrics. The recommended compliance process does require 2 different "sonar" metric collection runs. Hence, I would like to have sonar and compliance as different.

BTW, as we use maven and java, we collect sonar metrics by running sonar:sonar goal while building the code, so as to not to instrument/rerun tests.

-Ramesh Dara

Reply all
Reply to author
Forward
0 new messages