On Mon, May 22, 2017 at 11:38 AM, Daniel Belenky <dbelenky@redhat.com> wrote:

Hi all,

Please note that we've updated the default fallback repo in manual job.

The fallback repo defines the source from which the RPMs that are not part of the patch being tested are being taken.

Until today, the default source was 'latest_tested' repo, which is now replaced by 'latest_release'.

Note that 'latest_tested' repository shouldn't be used on regular basis, as this repository is changing as the

experimental flow runs, so in order to avoid failures - please use the stable 'latest_release' repo, which contains all the

rpm's that were released in the last official release of oVirt.

Does this apply to master branch too?

What if I run the manual job on a patch for the master branch of project A, that requires a package from a build of project B, that is newer than what's in the last release (or was not released yet at all)?

 

Thanks,

-- 

DANIEL BELENKY

Associate sw engineer

RHEV DEVOPS

Red Hat Israel

dbelenky@redhat.com    IRC: #rhev-integ, #rhev-dev

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

--

Didi