Re: [eclipse.org-project-leadership] Coverity Scan for Eclipse projects

["Pascal Rapicault" <pascal@xxxxxxxxxxxxx>]

And what about JIRA?

On Fri, May 31, 2013 15:34, Jason van Zyl wrote:
> Does this mean we can use Nexus Pro now at Eclipse?
>
> On May 31, 2013, at 3:22 PM, Ian Skerrett <ian.skerrett@xxxxxxxxxxx>
> wrote:
>
>> All,
>>
>> Coverity is providing a static analysis service, called Coverity Scan,
>> for open source projects. They have created a Hudson plugin that will
>> automatically start the scan of an Eclipse project during your build.
>>
>> We have installed this plugin on the Hudson sandbox server so Eclipse
>> projects can test the Coverity Scan service. Details on how to enable
>> the scan are below. If you have any questions, please contact Dakshesh
>> Vyas (dvyas@xxxxxxxxxxxx) from Coverity.
>>
>> Regards,
>> Ian Skerrett
>>
>>
>> Steps in brief:
>>
>> 1.      Add Coverity Scan plugin to your build process on
>> https://hudson.eclipse.org/sandbox/
>> 2.      Register your project with Coverity Scan
>> a.       Note - Make sure to use the same project name as the project
>> name in ‘Eclipse’ job
>> 3.      Enter the ‘Project token’ received at the end of registration
>> process into the build step of ‘Coverity Scan’ plugin
>> a.      Note - Project token and Project name is being used to check for
>> valid registration.
>> 4.      That’s it – Every time build is run, Coverity Scan will perform
>> static code analysis.
>>
>>
>> Steps in  Detail with Screenshot:-
>> 1.      Add Coverity Scan plugin to your build process on
>> https://hudson.eclipse.org/sandbox/
>> <image001.png>
>> 2.      Click on “Click here to register” to register your project with
>> Coverity Scan
>> 3.      Sign-up using your email address with Coverity Scan
>> <image002.png>
>> 4.      Confirm your email by clicking on the confirm email link.
>>                                                     i.
>> <image003.jpg>
>>
>> 5.      Click on “Add Project” and Register your project with Coverity
>> Scan
>>
>> <image004.png>
>> 6.      Note down the “Project token” under “Project Settings” page
>>
>> <image005.png>
>> 7.      Enter “Project token” in plug-in
>>
>> <image006.png>
>> 8.      Once the code is analyzed, you will be able to view the summary
>> defects directly in the plug-in. Details of the defects can be viewed by
>> sign-in to Coverity Scan.
>>
>> _______________________________________________
>> eclipse.org-project-leadership mailing list
>> eclipse.org-project-leadership@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership
>>
>> IMPORTANT: Membership in this list is generated by processes internal to
>> the Eclipse Foundation.  To be permanently removed from this list, you
>> must contactemo@xxxxxxxxxxx to request removal.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder & CTO, Sonatype
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
>
>
>
>
>
> _______________________________________________
> eclipse.org-project-leadership mailing list
> eclipse.org-project-leadership@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership
>
> IMPORTANT: Membership in this list is generated by processes internal to
> the Eclipse Foundation.  To be permanently removed from this list, you
> must contact emo@xxxxxxxxxxx to request removal.