5:26 a.m.
FYI,
As part of moving all jobs to the standard ci [1], I'd like to propose to
move the following into
'check-patch' and 'check-merged' :
1. unit tests
2. find-bugs
Currently these run as separate jobs and not even yamelized.
My only concern is populating junit & findbugs results into jenkins UI to
enable reviewing
the errors and continue to enforce logic from the original jobs, like '0'
high/med/low bugs on find-bugs.
Thoughts/Concerns?
--
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
4:51 a.m.
On Sun, Dec 13, 2015 at 12:26 PM, Eyal Edri <eedri(a)redhat.com> wrote:
FYI,
As part of moving all jobs to the standard ci [1], I'd like to propose to
move the following into
'check-patch' and 'check-merged' :
And [1] is?
- fabian
1. unit tests
2. find-bugs
Currently these run as separate jobs and not even yamelized.
My only concern is populating junit & findbugs results into jenkins UI to
enable reviewing
the errors and continue to enforce logic from the original jobs, like '0'
high/med/low bugs on find-bugs.
Thoughts/Concerns?
--
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--
Fabian Deutsch <fdeutsch(a)redhat.com>
RHEV Hypervisor
Red Hat
4:57 a.m.
On Mon, Dec 14, 2015 at 11:51 AM, Fabian Deutsch <fdeutsch(a)redhat.com>
wrote:
On Sun, Dec 13, 2015 at 12:26 PM, Eyal Edri <eedri(a)redhat.com>
wrote:
> FYI,
>
> As part of moving all jobs to the standard ci [1], I'd like to propose to
> move the following into
> 'check-patch' and 'check-merged' :
And [1] is?
[1] http://www.ovirt.org/CI/Build_and_test_standards
- fabian
> 1. unit tests
> 2. find-bugs
>
> Currently these run as separate jobs and not even yamelized.
>
> My only concern is populating junit & findbugs results into jenkins UI to
> enable reviewing
> the errors and continue to enforce logic from the original jobs, like '0'
> high/med/low bugs on find-bugs.
>
> Thoughts/Concerns?
>
> --
> Eyal Edri
> Supervisor, RHEV CI
> EMEA ENG Virtualization R&D
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
--
Fabian Deutsch <fdeutsch(a)redhat.com>
RHEV Hypervisor
Red Hat
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
5:01 a.m.
Thanks
On Mon, Dec 14, 2015 at 11:57 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
On Mon, Dec 14, 2015 at 11:51 AM, Fabian Deutsch <fdeutsch(a)redhat.com>
wrote:
>
> On Sun, Dec 13, 2015 at 12:26 PM, Eyal Edri <eedri(a)redhat.com> wrote:
> > FYI,
> >
> > As part of moving all jobs to the standard ci [1], I'd like to propose
> > to
> > move the following into
> > 'check-patch' and 'check-merged' :
>
> And [1] is?
[1] http://www.ovirt.org/CI/Build_and_test_standards
>
>
> - fabian
>
> > 1. unit tests
> > 2. find-bugs
> >
> > Currently these run as separate jobs and not even yamelized.
> >
> > My only concern is populating junit & findbugs results into jenkins UI
> > to
> > enable reviewing
> > the errors and continue to enforce logic from the original jobs, like
> > '0'
> > high/med/low bugs on find-bugs.
> >
> > Thoughts/Concerns?
> >
> > --
> > Eyal Edri
> > Supervisor, RHEV CI
> > EMEA ENG Virtualization R&D
> > Red Hat Israel
> >
> > phone: +972-9-7692018
> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
>
>
>
> --
> Fabian Deutsch <fdeutsch(a)redhat.com>
> RHEV Hypervisor
> Red Hat
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
--
Fabian Deutsch <fdeutsch(a)redhat.com>
RHEV Hypervisor
Red Hat
5:20 a.m.
My only concern is populating junit & findbugs results into jenkins UI to
enable reviewing
Since this came up a few times for different places recently, we
discussed this a little in our team meeting today.
Our current direction is to expand the CI-Standard a little so that if
'index.html' is placed in the exported-artifacts directory, it is read
and embedded into the jenkins build results screen.
This means that if you run such tools in check-patch, you need to make
them generate HTML reports and then place links to those reports in
the 'index.html' file.
Theoretically you can place any HTML in 'index.html' including result
tables, graphs, etc.
Note that everything above is subject to change, final details will be
determined only when we start having patches that try to implement
this.
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
3053
days inactive
3054
days old
4 comments
4 participants
participants (4)
-
Barak Korren -
Eyal Edri -
Fabian Deutsch -
Sandro Bonazzola