> On 22 Nov 2017, at 13:56, Barak Korren <[email protected]> wrote:
> 
> On 22 November 2017 at 13:14, Nir Soffer <[email protected] 
> <mailto:[email protected]>> wrote:
>> On Wed, Nov 22, 2017 at 9:17 AM Barak Korren <[email protected]> wrote:
>>> 
>>> On 22 November 2017 at 01:44, Greg Sheremeta <[email protected]> wrote:
>>>> 
>>>> Same thing really, but I like to navigate to
>>>> http://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/ and poke
>>>> around in the browser.
>>>> 
>>> There is not guarantee that what you see in the web UI resembles the
>>> actual yum repository structure in any way, this is why tools that
>>> actually read the yum metadata are preferable.
>> 
>> 
>> Can we write a tool that will take a spec and list of platforms and repos,
>> and verify that all the packages listed in the spec exist?
> 
> you mean like spectoo and yum-builddep?
> 
>> The main use case is RHEL - in the CI we are running on CentOS, with
>> EPEL repos, so we cannot detect missing packages.
>> 
>> Or maybe we should fix the CI repos so it simulates better a real system?
> 
> It simulates a very real CentOS, there is nothing to fix there.
> 
> I suppose you are talking about RHEL here. As a developer, when you
> add dependencies, its your responsibility to check that they exist on
> your target platforms and avoid adding them if they don’t.

True, though the point of CI is to make sure it actually happens, right:)

> We cannot
> really use RHEL on oVirt's CI, the developer's free license is only
> good for one laptop.

It does have a solution though. You work for Red Hat, you have a free license 
for machines in private network, you can place the jenkins slave there, and 
make it run RHEL test publishing results back to oVirt infra/gerrit

> 
> -- 
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com <http://redhat.com/> | TRIED. TESTED. TRUSTED. | 
> redhat.com/trusted <http://redhat.com/trusted>
> _______________________________________________
> Devel mailing list
> [email protected] <mailto:[email protected]>
> http://lists.ovirt.org/mailman/listinfo/devel 
> <http://lists.ovirt.org/mailman/listinfo/devel>
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel

Reply via email to