On Thu, May 5, 2016 at 11:05 AM, Roman Mohr <rmohr@redhat.com> wrote:

On Thu, May 5, 2016 at 9:48 AM, Yaniv Kaul <ykaul@redhat.com> wrote:

On Thu, May 5, 2016 at 10:42 AM, Roman Mohr <rmohr@redhat.com> wrote:

On Thu, May 5, 2016 at 9:32 AM, Eyal Edri <eedri@redhat.com> wrote:

Nice,

So its an online hosted Sonar instance for open source projects?

Exactly.

 

What about other projects in oVirt like VDSM?

We can ask them. Don't see any problems there.
I would just start with the engine and see how the whole process works.

On one hand Engine would be nice because we can compare it to Coverity.

On the other hand, I'd start with VDSM, as we don't have today something for it - and it's a smaller project.

I have not much experience with sonar and python. Further I don't know if travis support is already don for VDSM. There was a thread a few weeks ago regarding this topic.

Doing it with the engine will be very very easy for me. I can just do it while I work on other stuff ;)

I also suggest starting with the engine since the effort is small. Can they report by mail on severity?

Y.

 

E.

On Thu, May 5, 2016 at 10:13 AM, David Caro Estevez <dcaro@redhat.com> wrote:

On 05/05 09:13, David Caro Estevez wrote:
>
> Hey Roman,
>
> Adding the infra list

Forgot to add them XP

>
> On 05/05 08:57, Roman Mohr wrote:
> > Hi David,
> >
> > I have asked sonarqube if they would add ovirt-engine to
> > https://nemo.sonarqube.org/.
> >
> > sonarqube is a pretty nice tool for source code analysis. It has a slightly
> > different focus than coverity and could be very useful for us.
>
> Have you discussed this with the ovirt-engine maintainers/devs? Not that I
> think it would be an issue, but usually people don't like surprises :)
>
> >
> > They are happy to add us. In the past they just built everything on nemo
> > and published the results but they are switching to building on travis and
> > just upload the results.
> >
> > Do you think you could give me access to our ovirt-engine github repo?
>
> I can add the project, no problem, you can just make sure to create the new
> branch with the travis yaml (if noone has issues with it).
>
> >
> > I would do the following:
> >  - prepare a .travis.yml file on a separate branch
> >  - configure an account on nemo with the help of a sonarqube guy
>
> ^ the accounts are free? Can we create a project and add multiple admin
> accounts? If not, we should find a way to share that account to avoid a single
> maintainer
>
> >  - enable travis builds
> >  - when everything works I would add the .travis.yml file through a normal
> > gerrit patch
> >  - give up my github permissions if required ;)
> >
> > Roman
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
>
> Tel.: +420 532 294 605
> Email: dcaro@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605



--
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605

_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

--

Eyal Edri
Associate Manager

RHEV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)