How to stop Kojira on old EoL releases?

[John Florian]

I have a couple of private Koji instances I maintain that have the
Fedora repositories added as an external source via local mirrors.
When a Fedora releases reaches EoL, I follow along and to reduce disk
usage of the mirrors, I will delete the older releases. Recently F24
went this route but kojira still tries to run newRepo tasks against my
f24-build tag and fails because the mirror is gone. How can I stop
kojira for these older releases? I've tried lock-tag, but that didn't
seem to make any difference.
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to buildsys-***@lists.fedo

[Peter Robinson]

Post by John Florian
I have a couple of private Koji instances I maintain that have the
Fedora repositories added as an external source via local mirrors.
When a Fedora releases reaches EoL, I follow along and to reduce disk
usage of the mirrors, I will delete the older releases. Recently F24
went this route but kojira still tries to run newRepo tasks against my
f24-build tag and fails because the mirror is gone. How can I stop
kojira for these older releases? I've tried lock-tag, but that didn't
seem to make any difference.

Remove the associated build target
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to buildsys-le

[John Florian]

Post by Peter Robinson

Post by John Florian
I have a couple of private Koji instances I maintain that have the
Fedora repositories added as an external source via local mirrors.
When a Fedora releases reaches EoL, I follow along and to reduce disk
usage of the mirrors, I will delete the older releases. Recently F24
went this route but kojira still tries to run newRepo tasks against my
f24-build tag and fails because the mirror is gone. How can I stop
kojira for these older releases? I've tried lock-tag, but that didn't
seem to make any difference.

Remove the associated build target

Oh! That's simple enough. Thanks Peter! It also seems like a better
way to stop accidental builds than lock-tag. I wouldn't have guessed
this approach because other attempts to delete other things in Koji
invariably resulted in being denied due to references, i.e., foreign
key constraints (I presume).

Are there any other advisable steps to take for an EoL process (with
respect to Koji)? Doh! I just decided to google "fedora eol sop" and
quickly came across the answer to that Q and my original at:

https://docs.pagure.org/releng/sop_end_of_life.html
_______________________________________________
buildsys mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to buildsys-***@li