Could you please check the failing foreman-installer builds? Some of the
external repositories appear to be missing, probably the Puppet PC1 repo
which IIRC was configured on foreman-nightly-fedora24 and
foreman-nightly-nonscl-rhel7. Older versions used different
configurations though.
On 14/06/17 11:20, Lukas Zapletal wrote:
I haven't noticed builds in multiple (incorrect) tags yet. We will
need to look into that. We do have a koji running from backup (summer
2016) with the last tags from 1.12 release, do you think comparing
these to the new structure and deleting all extra builds would do the
trick?
If you're trying to determine the correct tag, use the whitelists in
rel-eng/tito.props, they are correct on recent branches. I don't think
that comparing to an old release is a good idea, packages occasionally move.
On 06/14/2017 06:20 AM, Lukas Zapletal wrote:
I assume the fix here is to go look at any package which is tagged into
foreman-nightly-$OS and then remove it from foreman-plugins-nightly-$OS. I am not sure about nonscl vs regular rhel 7. > It looks like those are peers so need to be double tagged?
I don't think any build should be tagged twice within one version. An
EL7 build should be tagged to foreman-nightly-rhel7 or
foreman-nightly-nonscl-rhel7.
There was tag inheritance set up between them, IIRC with foreman-release
in the build/srpm-build groups in both SCL and non-SCL tags. This looks
to be missing though.
--
Dominic Cleal
[email protected]
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
