I'm wondering if it's possible to import builds (via content generator) as
scratch builds, so they get cleaned up automatically at some point in the
We're working on a system that will be doing continuous development /
continuous delivery, and spans three different build systems. One is Koji,
but the other two will use Koji's content generator interface for passing
build data between the different systems.
We're trying to create a system where each PR triggers a whole workflow of
builds and test runs. However, in these cases we KNOW these are not
shippable builds, so we want to make them ephemeral in all of the build
systems. Obviously, cleanup tasks become a concern here, since we will
probably be doing many of these builds.
I think we could probably untag builds in Koji from an external system in
order to trigger GC of these temporary builds, but it seems like it would
be simpler to use a native cleanup routine in Koji.
Is this feasible?
This is Yuli for Brew/Koji Project PM.
Here we would like to invite you to join our first Koji community meeting
which is planned next Wed.(Dec 6)
Feel free to let me know or register in this docs if you are interested in
Welcome to Join.
I've filed  and subsequent PR . We send e-mails for most tagging
operations, but few are omitted from this standard workflow. Typically
those run by utility scripts like garbage collector, etc.
I would like in this PR to turn notification on in these scripts. It
changes API call un/tagBuildBypass to use notify=True default settings.
Do you think, that someone can be hurt by this change? Mike's sugestion
is that there could exists some rel-eng scripts doing mass-tagging and
thus generating tons of spam. Is this a case with some of you, or do you
think it is better to send notification whenever expected?
Tomas Kopecek <tkopecek(a)redhat.com>
Release Engineering Development, RedHat