Check which files are concerned by the changes
Locked
 
|
Hello,
We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page.
For example on the current version of a project we have 23282 info violations
When I choose in the time change selector the base version, the figures are the following = +23282 (in red).
When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those figures. They do not seem relevant.
If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar directly.
How can we identify the files that get the new violations?
We are using Sonar 2.13 and are planning to migrate to the new version.
Thanks in advance.
LORANT BENOIT
Consultant IT 
European Commission EuropeAid Cooperation Office Information Technologies and Infrastructure (R-6) L41 08/84 B-1049 Brussels/Belgium +32 2 29 57823 [hidden email] |
|
Lorant,
You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses: You've been trying this out for less than a month & you haven't made any changes to the differential periods.
So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything."
When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date. There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?" but also "is it getting better/worse."
Hope this helps. Let me know if my assumptions were wrong. Ann
On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote:
G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St.
Dalton Ga 30720 ****************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ****************************** |
|
|
Thank you for your answer Ann. Concerning the starting date for the Sonar project it's indeed the 14th of June, so less than one month
Changes have been made as there is a delta between today's violations and 14 th of June violations. Just below, I ask the delta between now (27/06/2012) and the 14th of June (our base line). I made the same calculation with over 5 days and over
30 days and the result is the same.
In the violation drill down I have the following errors and I don't understand what those figures in red means.
For example + 17 of blocker violations compare to what version ? If it is a comparaison between the base version and the current it is not correct as there
were from the beginning 17th blocking violations
Regards. Benoit From: Ann Campbell [mailto:[hidden email]]
Lorant, You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses: You've been trying this out for less than a month & you haven't made any changes to the differential periods. So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything." When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date. There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?"
but also "is it getting better/worse." Hope this helps. Let me know if my assumptions were wrong.
Ann On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote: Hello, We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page. For example on the current version of a project we have 23282 info violations When I choose in the time change selector the base version, the figures are the following = +23282 (in red). When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those
figures. They do not seem relevant. If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar
directly. How can we identify the files that get the new violations? We are using Sonar 2.13 and are planning to migrate to the new version. Thanks in advance. LORANT BENOIT
-- G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St. Dalton Ga 30720 ********************************************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible
for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business
of the company or its subsidiaries. ********************************************************** |
|
|
In general red and green always indicate a change over time. As you'd guess red means bad. Green means good.
You'll see "trend arrows" in your filters and dashboard when you don't have a differential period ("delta since") selected. In a very general way they indicate the trend over the last 30 days (that's a configurable period) for the metric they're next to. Some of these arrows are red/green, others are black for value-neutral metrics.
When you select a differential period, though, the focus of the interface changes to showing you what has changed in that time. So when you say "show me every violation since the project started" (which is essentially what you're doing) then it shows you in red (because violations are bad) for example, that 17 instances of "Cursor - Ensure locally opened cursors will be closed" have been added in that period. This will become more meaningful to you as you continue to use Sonar. But it might be illustrative for you to look at the "delta since last analysis" view - which will show you all the "brand new" violations that were added yesterday - rather than all the ones that showed up since your initial scan. On a slightly different topic, I notice from your screenshots that you're setting a different version stamp for each day's analysis. You may not want to do that. By changing the version every day, you're marking that analysis with an "event." Snapshots that have associated events don't get automatically cleaned out, so over time your database will bloat and your performance is likely to suffer if you continue as you're going.
I contribute to this list from my day job, so I don't usually feel free to do this, but you might benefit from the book Patroklos Papapetrou (another list member) and I are writing about Sonar. It's available from Manning in early release format right now: http://www.manning.com/papapetrou/
On Wed, Jun 27, 2012 at 9:48 AM, <[hidden email]> wrote:
G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St.
Dalton Ga 30720 ****************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ****************************** |
|
|
Hello again Ann, Can't we say that there is a problem in the way Sonar calculate the violations when we use the Time changes in the violation drill down. The first version (14 June 2012) contains 17 blocker violations.
When I compare the last version with the base version (the one from the 2012 Jun 14), I see
Blocker = + 17 Critical = 0 Major = + 1029 Minor = 0 Info = + 23316 And these are not relevant figures as there was already
17 blocker violations at the beginning Thanks. Benoit Lorant From: Ann Campbell [mailto:[hidden email]]
In general red and green always indicate a change over time. As you'd guess red means bad. Green means good. You'll see "trend arrows" in your filters and dashboard when you don't have a differential period ("delta since") selected. In a very general way they indicate the trend over the last 30 days (that's a configurable
period) for the metric they're next to. Some of these arrows are red/green, others are black for value-neutral metrics. When you select a differential period, though, the focus of the interface changes to showing you what has changed in that time. So when you say "show me every violation since the project started" (which is essentially
what you're doing) then it shows you in red (because violations are bad) for example, that 17 instances of "Cursor - Ensure locally opened cursors will be closed" have been added in that period. This will become more meaningful to you as you continue to use
Sonar. But it might be illustrative for you to look at the "delta since last analysis" view - which will show you all the "brand new" violations that were added yesterday - rather than all the ones that showed up since your initial scan. On a slightly different topic, I notice from your screenshots that you're setting a different version stamp for each day's analysis. You may not want to do that. By changing the version every day, you're marking
that analysis with an "event." Snapshots that have associated events don't get automatically cleaned out, so over time your database will bloat and your performance is likely to suffer if you continue as you're going. I contribute to this list from my day job, so I don't usually feel free to do this, but you might benefit from the book Patroklos Papapetrou (another list member) and I are writing about Sonar. It's available
from Manning in early release format right now: http://www.manning.com/papapetrou/ On Wed, Jun 27, 2012 at 9:48 AM, <[hidden email]> wrote:
Thank you for your answer Ann.
Concerning the starting date for the Sonar project it's indeed the 14th of June, so less than one month
Changes have been made as there is a delta between today's violations and 14 th of June violations.
Just below, I ask the delta between now (27/06/2012) and the 14th of June (our base line). I made the same calculation with over 5 days and over 30 days and the result
is the same.
In the violation drill down I have the following errors and I don't understand what those figures in red means.
For example + 17 of blocker violations compare to what version ? If it is a comparaison between the base version and the current it is not correct as there were from the beginning
17th blocking violations
Regards.
Benoit
From: Ann Campbell [mailto:[hidden email]]
Lorant,
You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses:
You've been trying this out for less than a month & you haven't made any changes to the differential periods.
So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything."
When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date.
There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?" but also "is it getting better/worse."
Hope this helps. Let me know if my assumptions were wrong.
Ann
On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote:
Hello,
We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page.
For example on the current version of a project we have 23282 info violations
When I choose in the time change selector the base version, the figures are the following = +23282 (in red).
When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those figures. They do not seem relevant.
If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar directly.
How can we identify the files that get the new violations?
We are using Sonar 2.13 and are planning to migrate to the new version.
Thanks in advance.
LORANT BENOIT
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
-- G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St. Dalton Ga 30720 ********************************************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible
for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business
of the company or its subsidiaries. ********************************************************** |
|
|
First, I'll agree that the differential results you get are a little odd looking when you compare to a time period that's before your first analysis.
I'm guessing that you're looking at the 30-day delta? I've got to ask when you last analyzed the project in question.
The reason I ask is that Sonar doesn't calculate these differential values on the fly. You're expecting that since 30 days have elapsed, the numbers will start to "normalize" as I promised. But Sonar doesn't do any calculations at page render time (by default. Some community widgets do a few small calculations.) Instead all those values are calculated as part of the analysis.So if your most recent analysis was from a week ago, then you're still looking at a differential that's measured against (before) day zero.
This facet of the underlying Sonar architecture is counter-intuitive and somewhat confusing, but I won't agree that it's wrong. I'm assuming it was made for performance reasons. Imagine 100 users trying to pull differential views at the same time if they were calculated on the fly. It doesn't seem like it should be that hard, but given the way my Jenkins/Sonar box lags during an analysis, I have to trust that there are good reasons for the decision.
On Mon, Jul 16, 2012 at 8:19 AM, <[hidden email]> wrote:
G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St.
Dalton Ga 30720 ****************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ****************************** |
|
|
The last analysis has been run on the 6th of July. The 1st analysis was run on the 14 th of June. It is the version that we use as the base line and that we inserted in the Time change select list.
In the Dashboard, when I use the time change, the figures are relevant. So for example, when I compare on the Dashboard the figures with the figures of June
14th, I got the following screen
But on the violations drill down page the figures don't seem to be relevant anymore. Or maybe there have another meaning that the one they have on the Dashboard. I click on the info link. Get the following screen
Then I change the Timechanges to "Added since 2012 Jun 14".
So maybe the meaning is completely different from the one I am expecting in the Dashboard. What I see is maybe the total amount of violations since the 14 th
of June. Benoit
From: Ann Campbell [mailto:[hidden email]]
First, I'll agree that the differential results you get are a little odd looking when you compare to a time period that's before your first analysis. I'm guessing that you're looking at the 30-day delta? I've got to ask when you last analyzed the project in question. The reason I ask is that Sonar doesn't calculate these differential values on the fly. You're expecting that since 30 days have elapsed, the numbers will start to "normalize" as I promised. But Sonar doesn't
do any calculations at page render time (by default. Some community widgets do a few small calculations.) Instead all those values are calculated as part of the analysis.So if your most recent analysis was from a week ago, then you're still looking at a differential
that's measured against (before) day zero. This facet of the underlying Sonar architecture is counter-intuitive and somewhat confusing, but I won't agree that it's wrong. I'm assuming it was made for performance reasons. Imagine 100 users trying to pull
differential views at the same time if they were calculated on the fly. It doesn't seem like it should be that hard, but given the way my Jenkins/Sonar box lags during an analysis, I have to trust that there are good reasons for the decision.
On Mon, Jul 16, 2012 at 8:19 AM, <[hidden email]> wrote:
Hello again Ann,
Can't we say that there is a problem in the way Sonar calculate the violations when we use the Time changes in the violation drill down.
The first version (14 June 2012) contains 17 blocker violations.
When I compare the last version with the base version (the one from the 2012 Jun 14), I see
Blocker = + 17
Critical = 0
Major = + 1029
Minor = 0
Info = + 23316
And these are not relevant figures as there was already
17 blocker violations at the beginning
Thanks.
Benoit Lorant
From: Ann Campbell [mailto:[hidden email]]
In general red and green always indicate a change over time. As you'd guess red means bad. Green means good.
You'll see "trend arrows" in your filters and dashboard when you don't have a differential period ("delta since") selected. In a very general way they indicate the trend over the last 30 days (that's a configurable period) for the metric they're next to. Some
of these arrows are red/green, others are black for value-neutral metrics.
When you select a differential period, though, the focus of the interface changes to showing you what has changed in that time. So when you say "show me every violation since the project started" (which is essentially what you're doing) then it shows you in
red (because violations are bad) for example, that 17 instances of "Cursor - Ensure locally opened cursors will be closed" have been added in that period. This will become more meaningful to you as you continue to use Sonar. But it might be illustrative for
you to look at the "delta since last analysis" view - which will show you all the "brand new" violations that were added yesterday - rather than all the ones that showed up since your initial scan.
On a slightly different topic, I notice from your screenshots that you're setting a different version stamp for each day's analysis. You may not want to do that. By changing the version every day, you're marking that analysis with an "event." Snapshots that
have associated events don't get automatically cleaned out, so over time your database will bloat and your performance is likely to suffer if you continue as you're going.
I contribute to this list from my day job, so I don't usually feel free to do this, but you might benefit from the book Patroklos Papapetrou (another list member) and I are writing about Sonar. It's available from Manning in early release format right now: http://www.manning.com/papapetrou/
On Wed, Jun 27, 2012 at 9:48 AM, <[hidden email]> wrote:
Thank you for your answer Ann.
Concerning the starting date for the Sonar project it's indeed the 14th of June, so less than one month
Changes have been made as there is a delta between today's violations and 14 th of June violations.
Just below, I ask the delta between now (27/06/2012) and the 14th of June (our base line). I made the same calculation with over 5 days and over 30 days and the result
is the same.
In the violation drill down I have the following errors and I don't understand what those figures in red means.
For example + 17 of blocker violations compare to what version ? If it is a comparaison between the base version and the current it is not correct as there were from the beginning
17th blocking violations
Regards.
Benoit
From: Ann Campbell [mailto:[hidden email]]
Lorant,
You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses:
You've been trying this out for less than a month & you haven't made any changes to the differential periods.
So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything."
When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date.
There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?" but also "is it getting better/worse."
Hope this helps. Let me know if my assumptions were wrong.
Ann
On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote:
Hello,
We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page.
For example on the current version of a project we have 23282 info violations
When I choose in the time change selector the base version, the figures are the following = +23282 (in red).
When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those figures. They do not seem relevant.
If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar directly.
How can we identify the files that get the new violations?
We are using Sonar 2.13 and are planning to migrate to the new version.
Thanks in advance.
LORANT BENOIT
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
-- G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St. Dalton Ga 30720 ********************************************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible
for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business
of the company or its subsidiaries. ********************************************************** |
|
|
Okay, I'm stumped by the disagreement between the dashboard and the drilldown.
Freddy?
On Mon, Jul 16, 2012 at 9:58 AM, <[hidden email]> wrote:
G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St.
Dalton Ga 30720 ****************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ****************************** |
|
In reply to this post by benoit.lorant
Hi,
This issue might be related to https://jira.codehaus.org/browse/SONAR-3647. Regards,
David RACODON | SonarSource
Senior Consultant On 16 July 2012 15:58, <[hidden email]> wrote:
|
|
|
In reply to this post by Ann Campbell
We found a workaround by setting 2 dates in the differential views. When we compare with the period 4, the figures are correct.
Regards. Benoit
From: Ann Campbell [mailto:[hidden email]]
Okay, I'm stumped by the disagreement between the dashboard and the drilldown. Freddy?
On Mon, Jul 16, 2012 at 9:58 AM, <[hidden email]> wrote:
The last analysis has been run on the 6th of July.
The 1st analysis was run on the 14 th of June. It is the version that we use as the base line and that we inserted in the Time change select list.
In the Dashboard, when I use the time change, the figures are relevant. So for example, when I compare on the Dashboard the figures with the figures of June 14th, I got
the following screen
But on the violations drill down page the figures don't seem to be relevant anymore. Or maybe there have another meaning that the one they have on the Dashboard.
I click on the info link. Get the following screen
Then I change the Timechanges to "Added since 2012 Jun 14".
So maybe the meaning is completely different from the one I am expecting in the Dashboard. What I see is maybe the total amount of violations since the 14 th of June.
Benoit
From: Ann Campbell [mailto:[hidden email]]
First, I'll agree that the differential results you get are a little odd looking when you compare to a time period that's before your first analysis.
I'm guessing that you're looking at the 30-day delta? I've got to ask when you last analyzed the project in question.
The reason I ask is that Sonar doesn't calculate these differential values on the fly. You're expecting that since 30 days have elapsed, the numbers will start to "normalize" as I promised. But Sonar doesn't do any calculations at page render time (by default.
Some community widgets do a few small calculations.) Instead all those values are calculated as part of the analysis.So if your most recent analysis was from a week ago, then you're still looking at a differential that's measured against (before) day zero.
This facet of the underlying Sonar architecture is counter-intuitive and somewhat confusing, but I won't agree that it's wrong. I'm assuming it was made for performance reasons. Imagine 100 users trying to pull differential views at the same time if they were
calculated on the fly. It doesn't seem like it should be that hard, but given the way my Jenkins/Sonar box lags during an analysis, I have to trust that there are good reasons for the decision.
On Mon, Jul 16, 2012 at 8:19 AM, <[hidden email]> wrote:
Hello again Ann,
Can't we say that there is a problem in the way Sonar calculate the violations when we use the Time changes in the violation drill down.
The first version (14 June 2012) contains 17 blocker violations.
When I compare the last version with the base version (the one from the 2012 Jun 14), I see
Blocker = + 17
Critical = 0
Major = + 1029
Minor = 0
Info = + 23316
And these are not relevant figures as there was already
17 blocker violations at the beginning
Thanks.
Benoit Lorant
From: Ann Campbell [mailto:[hidden email]]
In general red and green always indicate a change over time. As you'd guess red means bad. Green means good.
You'll see "trend arrows" in your filters and dashboard when you don't have a differential period ("delta since") selected. In a very general way they indicate the trend over the last 30 days (that's a configurable period) for the metric they're next to. Some
of these arrows are red/green, others are black for value-neutral metrics.
When you select a differential period, though, the focus of the interface changes to showing you what has changed in that time. So when you say "show me every violation since the project started" (which is essentially what you're doing) then it shows you in
red (because violations are bad) for example, that 17 instances of "Cursor - Ensure locally opened cursors will be closed" have been added in that period. This will become more meaningful to you as you continue to use Sonar. But it might be illustrative for
you to look at the "delta since last analysis" view - which will show you all the "brand new" violations that were added yesterday - rather than all the ones that showed up since your initial scan.
On a slightly different topic, I notice from your screenshots that you're setting a different version stamp for each day's analysis. You may not want to do that. By changing the version every day, you're marking that analysis with an "event." Snapshots that
have associated events don't get automatically cleaned out, so over time your database will bloat and your performance is likely to suffer if you continue as you're going.
I contribute to this list from my day job, so I don't usually feel free to do this, but you might benefit from the book Patroklos Papapetrou (another list member) and I are writing about Sonar. It's available from Manning in early release format right now: http://www.manning.com/papapetrou/
On Wed, Jun 27, 2012 at 9:48 AM, <[hidden email]> wrote:
Thank you for your answer Ann.
Concerning the starting date for the Sonar project it's indeed the 14th of June, so less than one month
Changes have been made as there is a delta between today's violations and 14 th of June violations.
Just below, I ask the delta between now (27/06/2012) and the 14th of June (our base line). I made the same calculation with over 5 days and over 30 days and the result
is the same.
In the violation drill down I have the following errors and I don't understand what those figures in red means.
For example + 17 of blocker violations compare to what version ? If it is a comparaison between the base version and the current it is not correct as there were from the beginning
17th blocking violations
Regards.
Benoit
From: Ann Campbell [mailto:[hidden email]]
Lorant,
You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses:
You've been trying this out for less than a month & you haven't made any changes to the differential periods.
So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything."
When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date.
There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?" but also "is it getting better/worse."
Hope this helps. Let me know if my assumptions were wrong.
Ann
On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote:
Hello,
We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page.
For example on the current version of a project we have 23282 info violations
When I choose in the time change selector the base version, the figures are the following = +23282 (in red).
When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those figures. They do not seem relevant.
If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar directly.
How can we identify the files that get the new violations?
We are using Sonar 2.13 and are planning to migrate to the new version.
Thanks in advance.
LORANT BENOIT
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
-- G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St. Dalton Ga 30720 ********************************************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible
for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business
of the company or its subsidiaries. ********************************************************** |
|
|
Hi there, Some other thing about this problem concerning the following problem :
https://jira.codehaus.org/browse/SONAR-3647. The metric does not always correspond when you compare the increase of violations on the Drilldown page and the violations you find on the dashboard page In the example below, the increase of the major is 0 in the Dashboard –
+11 for Info violations
the increase of the major is +2 in the Violations Drilldown info +31
From: [hidden email] [mailto:[hidden email]]
We found a workaround by setting 2 dates in the differential views. When we compare with the period 4, the figures are correct.
Regards. Benoit
From: Ann Campbell
[hidden email]
Okay, I'm stumped by the disagreement between the dashboard and the drilldown. Freddy?
On Mon, Jul 16, 2012 at 9:58 AM, <[hidden email]> wrote:
The last analysis has been run on the 6th of July.
The 1st analysis was run on the 14 th of June. It is the version that we use as the base line and that we inserted in the Time change select list.
In the Dashboard, when I use the time change, the figures are relevant. So for example, when I compare on the Dashboard the figures with the figures of June 14th, I got
the following screen
But on the violations drill down page the figures don't seem to be relevant anymore. Or maybe there have another meaning that the one they have on the Dashboard.
I click on the info link. Get the following screen
Then I change the Timechanges to "Added since 2012 Jun 14".
So maybe the meaning is completely different from the one I am expecting in the Dashboard. What I see is maybe the total amount of violations since the 14 th of June.
Benoit
From: Ann Campbell [mailto:[hidden email]]
First, I'll agree that the differential results you get are a little odd looking when you compare to a time period that's before your first analysis.
I'm guessing that you're looking at the 30-day delta? I've got to ask when you last analyzed the project in question.
The reason I ask is that Sonar doesn't calculate these differential values on the fly. You're expecting that since 30 days have elapsed, the numbers will start to "normalize" as I promised. But Sonar doesn't do any calculations at page render time (by default.
Some community widgets do a few small calculations.) Instead all those values are calculated as part of the analysis.So if your most recent analysis was from a week ago, then you're still looking at a differential that's measured against (before) day zero.
This facet of the underlying Sonar architecture is counter-intuitive and somewhat confusing, but I won't agree that it's wrong. I'm assuming it was made for performance reasons. Imagine 100 users trying to pull differential views at the same time if they were
calculated on the fly. It doesn't seem like it should be that hard, but given the way my Jenkins/Sonar box lags during an analysis, I have to trust that there are good reasons for the decision.
On Mon, Jul 16, 2012 at 8:19 AM, <[hidden email]> wrote:
Hello again Ann,
Can't we say that there is a problem in the way Sonar calculate the violations when we use the Time changes in the violation drill down.
The first version (14 June 2012) contains 17 blocker violations.
When I compare the last version with the base version (the one from the 2012 Jun 14), I see
Blocker = + 17
Critical = 0
Major = + 1029
Minor = 0
Info = + 23316
And these are not relevant figures as there was already
17 blocker violations at the beginning
Thanks.
Benoit Lorant
From: Ann Campbell [mailto:[hidden email]]
In general red and green always indicate a change over time. As you'd guess red means bad. Green means good.
You'll see "trend arrows" in your filters and dashboard when you don't have a differential period ("delta since") selected. In a very general way they indicate the trend over the last 30 days (that's a configurable period) for the metric they're next to. Some
of these arrows are red/green, others are black for value-neutral metrics.
When you select a differential period, though, the focus of the interface changes to showing you what has changed in that time. So when you say "show me every violation since the project started" (which is essentially what you're doing) then it shows you in
red (because violations are bad) for example, that 17 instances of "Cursor - Ensure locally opened cursors will be closed" have been added in that period. This will become more meaningful to you as you continue to use Sonar. But it might be illustrative for
you to look at the "delta since last analysis" view - which will show you all the "brand new" violations that were added yesterday - rather than all the ones that showed up since your initial scan.
On a slightly different topic, I notice from your screenshots that you're setting a different version stamp for each day's analysis. You may not want to do that. By changing the version every day, you're marking that analysis with an "event." Snapshots that
have associated events don't get automatically cleaned out, so over time your database will bloat and your performance is likely to suffer if you continue as you're going.
I contribute to this list from my day job, so I don't usually feel free to do this, but you might benefit from the book Patroklos Papapetrou (another list member) and I are writing about Sonar. It's available from Manning in early release format right now: http://www.manning.com/papapetrou/
On Wed, Jun 27, 2012 at 9:48 AM, <[hidden email]> wrote:
Thank you for your answer Ann.
Concerning the starting date for the Sonar project it's indeed the 14th of June, so less than one month
Changes have been made as there is a delta between today's violations and 14 th of June violations.
Just below, I ask the delta between now (27/06/2012) and the 14th of June (our base line). I made the same calculation with over 5 days and over 30 days and the result
is the same.
In the violation drill down I have the following errors and I don't understand what those figures in red means.
For example + 17 of blocker violations compare to what version ? If it is a comparaison between the base version and the current it is not correct as there were from the beginning
17th blocking violations
Regards.
Benoit
From: Ann Campbell [mailto:[hidden email]]
Lorant,
You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses:
You've been trying this out for less than a month & you haven't made any changes to the differential periods.
So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything."
When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date.
There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?" but also "is it getting better/worse."
Hope this helps. Let me know if my assumptions were wrong.
Ann
On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote:
Hello,
We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page.
For example on the current version of a project we have 23282 info violations
When I choose in the time change selector the base version, the figures are the following = +23282 (in red).
When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those figures. They do not seem relevant.
If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar directly.
How can we identify the files that get the new violations?
We are using Sonar 2.13 and are planning to migrate to the new version.
Thanks in advance.
LORANT BENOIT
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
-- G. Ann Campbell Sr. Systems Engineer, IS Production Systems - Shop Floor Systems Shaw Industries Inc, 201 S. Hamilton St. Dalton Ga 30720 ********************************************************** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible
for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business
of the company or its subsidiaries. ********************************************************** |
|
|
Hi Benoit,
The dashboard (screenshot #1) displays the overall number of violations. If you have 11 more violations, it could mean:
In your case, you have 0 more major violations, meaning that you have added 2 (screenshot #2) and fixed 2. The violations drilldown only shows added violations (so the two major ones) to help you focus on technical debt you just added.
If you update to a newer version of Sonar, you'll get two more pieces of information to help you better understand this behavior:  Regards, David RACODON | SonarSource
Senior Consultant On 20 July 2012 12:11, <[hidden email]> wrote:
|
|
|
Hi David, Thank you for your answer but would it be possible that there is a problem when calculating in the violations drilldown. Look at that example here.
When I clicked on the Info link to get the violations drilldown info, I got the following screen
Then I put the time change on the 14th of June and the figures are not relevant anymore.
Regards. Benoit
From: David Racodon
[hidden email]
Hi Benoit, The dashboard (screenshot #1) displays the overall number of violations. If you have 11 more violations, it could mean:
·
You fixed 0 violation and added 11
·
You fixed 10 violations and added 21 In your case, you have 0 more major violations, meaning that you have added 2 (screenshot #2) and fixed 2. The violations drilldown only shows added violations (so the two major ones) to help you focus on technical debt you just added. If you update to a newer version of Sonar, you'll get two more pieces of information to help you better understand this behavior: Regards,
David RACODON | SonarSource
On 20 July 2012 12:11, <[hidden email]> wrote:
Hi there,
Some other thing about this problem concerning the following problem :
https://jira.codehaus.org/browse/SONAR-3647.
The metric does not always correspond when you compare the increase of violations on the Drilldown page and the violations you find on the dashboard page
In the example below, the increase of the major is 0 in the Dashboard –
+11 for Info violations
the increase of the major is +2 in the Violations Drilldown
info +31
From:
[hidden email] [mailto:[hidden email]]
We found a workaround by setting 2 dates in the differential views.
When we compare with the period 4, the figures are correct.
Regards.
Benoit
From: Ann Campbell
[hidden email]
Okay, I'm stumped by the disagreement between the dashboard and the drilldown.
Freddy?
On Mon, Jul 16, 2012 at 9:58 AM, <[hidden email]> wrote:
The last analysis has been run on the 6th of July.
The 1st analysis was run on the 14 th of June. It is the version that we use as the base line and that we inserted in the Time change select list.
In the Dashboard, when I use the time change, the figures are relevant. So for example, when I compare on the Dashboard the figures with the figures of June 14th, I got
the following screen
But on the violations drill down page the figures don't seem to be relevant anymore. Or maybe there have another meaning that the one they have on the Dashboard.
I click on the info link. Get the following screen
Then I change the Timechanges to "Added since 2012 Jun 14".
So maybe the meaning is completely different from the one I am expecting in the Dashboard. What I see is maybe the total amount of violations since the 14 th of June.
Benoit
From: Ann Campbell [mailto:[hidden email]]
First, I'll agree that the differential results you get are a little odd looking when you compare to a time period that's before your first analysis.
I'm guessing that you're looking at the 30-day delta? I've got to ask when you last analyzed the project in question.
The reason I ask is that Sonar doesn't calculate these differential values on the fly. You're expecting that since 30 days have elapsed, the numbers will start to "normalize" as I promised. But Sonar doesn't do any calculations at page render time (by default.
Some community widgets do a few small calculations.) Instead all those values are calculated as part of the analysis.So if your most recent analysis was from a week ago, then you're still looking at a differential that's measured against (before) day zero.
This facet of the underlying Sonar architecture is counter-intuitive and somewhat confusing, but I won't agree that it's wrong. I'm assuming it was made for performance reasons. Imagine 100 users trying to pull differential views at the same time if they were
calculated on the fly. It doesn't seem like it should be that hard, but given the way my Jenkins/Sonar box lags during an analysis, I have to trust that there are good reasons for the decision.
On Mon, Jul 16, 2012 at 8:19 AM, <[hidden email]> wrote:
Hello again Ann,
Can't we say that there is a problem in the way Sonar calculate the violations when we use the Time changes in the violation drill down.
The first version (14 June 2012) contains 17 blocker violations.
When I compare the last version with the base version (the one from the 2012 Jun 14), I see
Blocker = + 17
Critical = 0
Major = + 1029
Minor = 0
Info = + 23316
And these are not relevant figures as there was already
17 blocker violations at the beginning
Thanks.
Benoit Lorant
From: Ann Campbell [mailto:[hidden email]]
In general red and green always indicate a change over time. As you'd guess red means bad. Green means good.
You'll see "trend arrows" in your filters and dashboard when you don't have a differential period ("delta since") selected. In a very general way they indicate the trend over the last 30 days (that's a configurable period) for the metric they're next to. Some
of these arrows are red/green, others are black for value-neutral metrics.
When you select a differential period, though, the focus of the interface changes to showing you what has changed in that time. So when you say "show me every violation since the project started" (which is essentially what you're doing) then it shows you in
red (because violations are bad) for example, that 17 instances of "Cursor - Ensure locally opened cursors will be closed" have been added in that period. This will become more meaningful to you as you continue to use Sonar. But it might be illustrative for
you to look at the "delta since last analysis" view - which will show you all the "brand new" violations that were added yesterday - rather than all the ones that showed up since your initial scan.
On a slightly different topic, I notice from your screenshots that you're setting a different version stamp for each day's analysis. You may not want to do that. By changing the version every day, you're marking that analysis with an "event." Snapshots that
have associated events don't get automatically cleaned out, so over time your database will bloat and your performance is likely to suffer if you continue as you're going.
I contribute to this list from my day job, so I don't usually feel free to do this, but you might benefit from the book Patroklos Papapetrou (another list member) and I are writing about Sonar. It's available from Manning in early release format right now: http://www.manning.com/papapetrou/
On Wed, Jun 27, 2012 at 9:48 AM, <[hidden email]> wrote:
Thank you for your answer Ann.
Concerning the starting date for the Sonar project it's indeed the 14th of June, so less than one month
Changes have been made as there is a delta between today's violations and 14 th of June violations.
Just below, I ask the delta between now (27/06/2012) and the 14th of June (our base line). I made the same calculation with over 5 days and over 30 days and the result
is the same.
In the violation drill down I have the following errors and I don't understand what those figures in red means.
For example + 17 of blocker violations compare to what version ? If it is a comparaison between the base version and the current it is not correct as there were from the beginning
17th blocking violations
Regards.
Benoit
From: Ann Campbell [mailto:[hidden email]]
Lorant,
You don't say how long you've been using Sonar or what your differential periods are, so I'm going to make some guesses:
You've been trying this out for less than a month & you haven't made any changes to the differential periods.
So when you pick the last option in the "Time changes..." dropdown, you're asking to see everything that's changed in the last 30 days. And since you've been at it for less than a month, the answer is "everything."
When you look at the "delta since 2012 June 14" Sonar is showing you that 23 violations have been added since that date.
There are a lot of code quality tools out there that will give you a "current state" reading, but one of the beautiful things about Sonar is that you get trending too. Not just "how good/bad does it look today?" but also "is it getting better/worse."
Hope this helps. Let me know if my assumptions were wrong.
Ann
On Tue, Jun 26, 2012 at 9:49 AM, <[hidden email]> wrote:
Hello,
We do an analysis of files every day for each release on which teams are working.
When we look to the figures, there don't seem correct on the violations drilldown page.
For example on the current version of a project we have 23282 info violations
When I choose in the time change selector the base version, the figures are the following = +23282 (in red).
When I go back on the dashboard, after I select the base line (delta since 2012 Jun 14) I got 23,283 (+23 in red). What is the meaning of those figures. They do not seem relevant.
If we want to know which files contains the new violations, should we get to mysql the database or is there a way to get the answer through Sonar directly.
How can we identify the files that get the new violations?
We are using Sonar 2.13 and are planning to migrate to the new version.
Thanks in advance.
LORANT BENOIT
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
--
G. Ann Campbell
Sr. Systems Engineer, IS Production Systems - Shop Floor Systems
Shaw Industries Inc,
201 S. Hamilton St.
Dalton Ga 30720
**********************************************************
Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person)
, you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail.
If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.
Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
**********************************************************
|
|
|
Hi,
Isn't it the example from the beginning of this thread. Is June 14th, the fist analysis of this projetct? If so, as discussed, it must be related to https://jira.codehaus.org/browse/SONAR-3647.
Regards, David RACODON | SonarSource
Senior Consultant On 20 July 2012 17:10, <[hidden email]> wrote:
|
| Powered by Nabble | Edit this page |