So to give a little more context, bodhi in staging has support for single-build gating. So when building a package in rawhide it will land in a tag (f31-updates-candidate) where it'll wait. Bodhi will pick it up, create an update with it, if the tests pass or if there are no tests, the update will be pushed to rawhide as it is today, so basically pushed to f31-pending to be signed and pushed.

Which means, of all the tags requested, only f31-updates-candidate may be needed, but we are double-checking as it could be that bodhi asks for them even though it won't make use of them.

So after thinking about it a little bit with @pingou, I think we want the following flow

f31-build (new build in koji) --> f31-updates-candidate (bodhi automatically creates the update) --> bodhi open the gates --> f31-pending --> robosignatory signs the builds --> f31 ( the build is available for next compose)

So I think we need to change the current f31 --dest-tag to f31-updates-candidate tag instead of f31-pending.

We could probably change f31-pending to f31-updates-pending but this will require a change in robosignatory so that it listen to the f31-updates-pending tag.

Just one question, for 700 of packages I have tests. How would I push them to rawhide nowadays if bodhi would create update for each one separately and they obviously won't work. I'm not even sure that tests are working today because I did not look how CI is broken for like half a year. It might be also possible that tests themselves are broken too.

Just one question, for 700 of packages I have tests. How would I push them to rawhide nowadays if bodhi would create update for each one separately and they obviously won't work. I'm not even sure that tests are working today because I did not look how CI is broken for like half a year. It might be also possible that tests themselves are broken too.

I am not 100% sure I get the question, but we are not ready for multi package update in bodhi yet we are working on it. But this change is for staging only and will not be apply to production until we have multi package update. We just need to test single build update early.

Does that answer the question ?

Good enough for now, thanks. I'm still curious how multi-package update is supposed to work, but this is out of this tickets’ scope.

The tags are created in stg koji a while back by me (but I forgot why) but to do some testing.

Now changed the targets:

$ stg-koji edit-target f31 --dest-tag f31-updates-candidate
$ stg-koji edit-target f31-candidate --dest-tag f31-updates-candidate
$ stg-koji edit-target rawhide --dest-tag f31-updates-candidate

Let me know if you want anything else.

Thanks