Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[venkatakrishnan nagarajan]

How about displaying the HTML report files under Violation report? If yes 
> then how to configure.

But am able to display the HTML files under Post Build Actions-> Archive 
the artifacts.

Thanks

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/18769566-7c6b-42be-93e2-a89555185a8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[Daniel Beck]

> On 18.10.2016, at 09:48, venkatakrishnan nagarajan 
>  wrote:
> 
> Hi, As am unware of java stuff, I explored python to create new plugin. I 
> havent got any hint nowhere. 

That's because it's not possible.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ADE91F11-0E9F-4EE4-82C0-2A384C781F85%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[venkatakrishnan nagarajan]

Hi, As am unware of java stuff, I explored python to create new plugin. I 
havent got any hint nowhere. 
Is there any possibility to display my own files like HTML/BMP/XML in 
violation report plugin?

Thanks

On Tuesday, October 4, 2016 at 4:48:09 PM UTC, Daniel Beck wrote:
>
>
> > On 04.10.2016, at 15:03, venkatakrishnan nagarajan  > wrote: 
> > 
> > For developing new plug-in, do we need editor to write java 
> code(eclipse) to start  or python? Kindly suggest the steps 
>
> There is plenty of documentation on how to get started with Jenkins plugin 
> development available in our wiki and elsewhere. Just google it. 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7dbf27e7-ad52-4e19-9afd-0a83f5d2b059%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[Daniel Beck]

> On 04.10.2016, at 15:03, venkatakrishnan nagarajan 
>  wrote:
> 
> For developing new plug-in, do we need editor to write java code(eclipse) to 
> start  or python? Kindly suggest the steps

There is plenty of documentation on how to get started with Jenkins plugin 
development available in our wiki and elsewhere. Just google it.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5DC0AE50-5A2A-4328-98EA-301AB0CE38F8%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[venkatakrishnan nagarajan]

Hi,
As we are obliged with our client we cannot take decisions on our own to go 
for CPD or Simian but any way we can suggest later.
Am an Microsoft developer. For developing new plug-in, do we need editor to 
write java code(eclipse) to start  or python? Kindly suggest the steps.
Could you please advise on how to start initial coding with the new plugin.

Thanks,
Venkat

On Tuesday, October 4, 2016 at 8:45:21 AM UTC, Ullrich Hafner wrote:
>
> It would be simpler to change your duplicate code scanner and metrics tool 
> to one that is already supported by Jenkins. Did you look at CPD or Simian 
> for code duplications? Or Jenkins metrics plug-in?
>
> If you are planning to write a new plug-in, see 
> http://wiki.jenkins-ci.org/.
>
> If you are planning to write a new parser, see 
> https://github.com/jenkinsci/dry-plugin/tree/master/src/main/java/hudson/plugins/dry/parser
>  
> for some examples. Here no tutorial is available.
>
> Am 04.10.2016 um 09:15 schrieb venkatakrishnan nagarajan <
> venket@gmail.com >:
>
> Since am new to JEnkins, am not aware of writing parser or developing new 
> Plug-in. Is there any development tutorials available?
> Kindly help on this.
>
>
>
> On Monday, October 3, 2016 at 2:58:20 PM UTC, Ullrich Hafner wrote:
>>
>> For Atomiq Console you need to write a parser for the dry plug-in (
>> https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin).
>> For Source Monitor you need to write a new plug-in.
>>  
>>
>> Am 03.10.2016 um 15:26 schrieb venkatakrishnan nagarajan <
>> venket@gmail.com>:
>>
>> Hi all,
>>
>> Currently i have developed application exe which does the static code 
>> analysis part using FxCop, Atomiq Console and Source Monitor.
>> When i tried to run my application  exe in jenkins  am able to generate 
>> report for all the three (FxCop, Atomiq Console and Source Monitor).
>> Through jenkins violation plugin only for FxCop am able to show the 
>> violation report for the respective build but not for ATOMIQ CONSOLE and 
>> SOURCE MONITOR
>> Could you please help me how to show the violation report in Jenkins for 
>> Atomiq console and source monitor in the same build version
>>
>> Thanks,
>> Venkat
>>
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/f95c9135-00c3-43a0-b540-b021ae76a53e%40googlegroups.com
>>  
>> 
>> .
>> 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-de...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/f651d74e-bd3e-4a84-94c1-c70a7d2c017e%40googlegroups.com
>  
> 
> .
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e7ef7daa-2fac-464b-b8b3-fed04abcdc08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[Ullrich Hafner]

It would be simpler to change your duplicate code scanner and metrics tool to 
one that is already supported by Jenkins. Did you look at CPD or Simian for 
code duplications? Or Jenkins metrics plug-in?

If you are planning to write a new plug-in, see http://wiki.jenkins-ci.org/.

If you are planning to write a new parser, see 
https://github.com/jenkinsci/dry-plugin/tree/master/src/main/java/hudson/plugins/dry/parser
 for some examples. Here no tutorial is available.

> Am 04.10.2016 um 09:15 schrieb venkatakrishnan nagarajan 
> :
> 
> Since am new to JEnkins, am not aware of writing parser or developing new 
> Plug-in. Is there any development tutorials available?
> Kindly help on this.
> 
> 
> 
> On Monday, October 3, 2016 at 2:58:20 PM UTC, Ullrich Hafner wrote:
> For Atomiq Console you need to write a parser for the dry plug-in 
> (https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin 
> ).
> For Source Monitor you need to write a new plug-in.
>  
>> Am 03.10.2016 um 15:26 schrieb venkatakrishnan nagarajan 
>> :
>> 
>> Hi all,
>> 
>> Currently i have developed application exe which does the static code 
>> analysis part using FxCop, Atomiq Console and Source Monitor.
>> When i tried to run my application  exe in jenkins  am able to generate 
>> report for all the three (FxCop, Atomiq Console and Source Monitor).
>> Through jenkins violation plugin only for FxCop am able to show the 
>> violation report for the respective build but not for ATOMIQ CONSOLE and 
>> SOURCE MONITOR
>> Could you please help me how to show the violation report in Jenkins for 
>> Atomiq console and source monitor in the same build version
>> 
>> Thanks,
>> Venkat
>> 
>> 
>> -- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/f95c9135-00c3-43a0-b540-b021ae76a53e%40googlegroups.com
>>  
>> .
>> 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+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/f651d74e-bd3e-4a84-94c1-c70a7d2c017e%40googlegroups.com
>  
> .
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/BF39EC2A-E0E0-4ECA-8930-BB4983E9CFAE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[venkatakrishnan nagarajan]

Since am new to JEnkins, am not aware of writing parser or developing new 
Plug-in. Is there any development tutorials available?
Kindly help on this.



On Monday, October 3, 2016 at 2:58:20 PM UTC, Ullrich Hafner wrote:
>
> For Atomiq Console you need to write a parser for the dry plug-in (
> https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin).
> For Source Monitor you need to write a new plug-in.
>  
>
> Am 03.10.2016 um 15:26 schrieb venkatakrishnan nagarajan <
> venket@gmail.com >:
>
> Hi all,
>
> Currently i have developed application exe which does the static code 
> analysis part using FxCop, Atomiq Console and Source Monitor.
> When i tried to run my application  exe in jenkins  am able to generate 
> report for all the three (FxCop, Atomiq Console and Source Monitor).
> Through jenkins violation plugin only for FxCop am able to show the 
> violation report for the respective build but not for ATOMIQ CONSOLE and 
> SOURCE MONITOR
> Could you please help me how to show the violation report in Jenkins for 
> Atomiq console and source monitor in the same build version
>
> Thanks,
> Venkat
>
>
> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/f95c9135-00c3-43a0-b540-b021ae76a53e%40googlegroups.com
>  
> 
> .
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f651d74e-bd3e-4a84-94c1-c70a7d2c017e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Violations Report for Atomiq - Code Similarity Finder and SOurce Monitor

[Ullrich Hafner]

For Atomiq Console you need to write a parser for the dry plug-in 
(https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin).
For Source Monitor you need to write a new plug-in.
 
> Am 03.10.2016 um 15:26 schrieb venkatakrishnan nagarajan 
> :
> 
> Hi all,
> 
> Currently i have developed application exe which does the static code 
> analysis part using FxCop, Atomiq Console and Source Monitor.
> When i tried to run my application  exe in jenkins  am able to generate 
> report for all the three (FxCop, Atomiq Console and Source Monitor).
> Through jenkins violation plugin only for FxCop am able to show the violation 
> report for the respective build but not for ATOMIQ CONSOLE and SOURCE MONITOR
> Could you please help me how to show the violation report in Jenkins for 
> Atomiq console and source monitor in the same build version
> 
> Thanks,
> Venkat
> 
> 
> -- 
> 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+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/f95c9135-00c3-43a0-b540-b021ae76a53e%40googlegroups.com
>  
> .
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/21CE0221-DB91-4D5B-8B0B-C687FF118C4C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.