Excerpts from Nick Coghlan's message of 2014-08-12 14:18 +10:00:
On 08/12/2014 10:47 AM, Dan Callaghan wrote:
> 4. Modify the distro picking logic in bkr machine-test so that if
> --family is not given, we just pick the newest matching tree from
> *any* family. So that effectively means RHEL7 or Fedora will be
> picked unless it's an arch that doesn't have those (ia64) in which
> case RHEL5 will be picked.
I'm not sure this part follows. The problem I see is that the long
maintenance cycle for RHEL means we're still regularly seeing new trees
for RHEL 5, 6 *and* 7. At any given point in time, the most recently
imported nightly build could be from any one of them.
Even switching to "only released trees" wouldn't help, since the latest
5.x or 6.y may be newer than the most recent 7.z release.
However, while I don't see how we can make it implicit based on when
trees were imported, I think (given points 1->3 above) we *could* just
make a configurable "preferred distro family for inventory scanning"
list that runs something like:
RedHatEnterpriseLinux7
CentOS7
RedHatEnterpriseLinux6
CentOS6
RedHatEnterpriseLinux5
CentOS5
Fedora20
Hmm yes I was trying to avoid having to have a hardcoded list like that,
but you're right about the nightly timestamps. So this might be
unavoidable.
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.