> On Weds next week there will be some disruption to Foreman's nightly
> plugin tags, as I attempt to add a non-SCL set of tags and buildroots.
> I'll try to keep it to a minimum, but please avoid building new plugin
> packages while it's happening.
This is now complete, let me know if you see any unexpected RPM build
failures on Koji. Both SCL and non-SCL plugins seem to be building OK.
> As part of https://github.com/theforeman/foreman-packaging/pull/736,
> Stephen's trying to build an additional non-SCL version of
> rubygem-dynflow, so this will need separate tags build both versions.
> I'll be creating new nonscl variants, moving existing non-SCL builds to
> these tags and then setting foreman-plugin-nightly-rhel* to inherit from
> the nonscl tags.
I didn't do this precisely - instead, I set
foreman-plugin-nightly-rhel*-build to inherit from the nonscl tags
explicitly. This makes cloning for releases much easier as cloning the
SCL tag won't then also keep the inherited nonscl builds.
http://koji.katello.org/koji/taginfo?tagID=403 (plugins SCL build)
http://koji.katello.org/koji/taginfo?tagID=786 (plugins non-SCL build)
I also changed foreman-nightly-rhel* to work in the same way for
consistency. It no longer inherits from nonscl, but only its build tag
http://koji.katello.org/koji/taginfo?tagID=397 (foreman SCL build)
In the unlikely event that another tag (Katello?) needs access to
non-SCL builds inside buildroots, then run "kkoji add-tag-inheritance
–priority=15 example-build foreman-nightly-nonscl-rhel6" and again for
foreman-plugins-nightly-nonscl-rhel6, to explicitly add the nonscl tags
to the build tags.
> Then I'll update tito configs in rpm/develop to send
> non-SCL plugin packages to the new build target, and mash configs to
> generate the repos from both tags.
Done, "tito release koji-foreman-plugins" will still work automatically
using the whitelists in tito.props to send packages to the right tags.
The only difference for users will be that there are two plugin
whitelists, an SCL one and a non-SCL one.
On 14/08/15 10:17, Dominic Cleal wrote:
Red Hat Engineering