WE have been working automating the bodhi release process somewhat, and have settled on a GitHub Actions based solution for building staging versions of the bodhi packages in Koji. It is currently working (scratch builds, using a new user "bodhibuilder")
so, for this ticket, there are a few questions / requests:
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
The PR has changed. the file to review is now: https://github.com/fedora-infra/bodhi/pull/4393/files#diff-7bb7a67ed05f3845ed1f1b92dc4b87dfb0dd9aba208cca5489055ccef315117b
I'll note too that packit did not suit our needs for two reasons:
ok, a few things.
Could you follow https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/#_bot_accounts for the bot account? ie, ends in -bot and has a wiki page listing what it does, who it's for, who controls it, etc?
This is just staging right? So, it will update staging but still needs a human to 'koji move-build' into the prod tag? Or is that planned to be automated too?
Otherwise seems ok to me. I can grant it infra perms in koji when it's ready...
ok, a few things. Could you follow https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/#_bot_accounts for the bot account? ie, ends in -bot and has a wiki page listing what it does, who it's for, who controls it, etc?
Ok, have created a new user bodhidev-bot that we will use here. Furthermore., Is it possible to remove the old bodhibuilder user?
bodhidev-bot
I think for now, would like to keep the automation process to just be on staging. We will probably want to keep the tagging into stable as a manual process for now.
It might be possible, but I'd say lets just deactivate it and leave it at that?
Sounds good. I have added 'infra' perm to bodhidev-bot now. :)
Let me know if you need anything else!
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.