Hi, I'm a current fedora packager. I created the 'rhcontainerbot' account which I'm hoping to use as the packager in automated rpm builds. Could you please sponsor this into the packager group?
I support this message :thumbsup:
Could you please provide more details about this automation?
So, I have a CI job running at https://gitlab.com/lsm5/rpm-builder for automating rpm builds for podman and other container related tools. Jobs run hourly and build latest upstream master for rawhide and latest tags for other fedora branches. Currently uses my 'lsm5' account's krb. But I'd prefer not using my primary account in unmanned builds.
As a side note, do you realize all your rawhide builds are gated? https://bodhi.fedoraproject.org/updates/?packages=podman
+1 for the account as long as you are still responsible for the bot's actions and you get e-mail directed to the bot via rhcontainerbot@fedoraproject.org.
I'd like to know whether hourly builds are OK by infra people, but since you are already doing this, it shall not block the bot sponsoring.
yup :D , that's on my TODO with @santiago
+1 for the account as long as you ares till responsible for the bots actions and you get e-mail directed to the bot via rhcontainerbot@fedoraproject.org.
Yes, I have access to the email used and I'll be responsible for it. The FAS2 account page mentions my primary account in there so people can know that they should be reaching out to me if anything.
I'd like to now whether hourly builds are OK by infra people, but since you are already doing this, it shall not block the bot sponsoring.
Ack, thanks. If infra people object, I can build less frequently.
I'd like to now whether hourly builds are OK by infra people, but since you are already doing this, it shall not block the bot sponsoring. Ack, thanks. If infra people object, I can build less frequently.
Well, rawhide itself only composes once a day, so the rest of the builds wouldn't be distributed (but of course you could still test them/have them for whatever reason). Perhaps it would be worthwhile to change it to check once an hour and only build if there were new commits since the last build? Or just build it once a day, early in the day, but that depends on what you want to use the builds for I guess.
Perhaps it would be worthwhile to change it to check once an hour and only build if there were new commits since the last build?
Yes, that's already happening :) For example: https://gitlab.com/lsm5/rpm-builder/-/jobs/295192702
+1
Just curious, @ttomecek is advocating for packit everywhere. Should not it be better to use that instead of creating your own bots?
packit
I'm +0 on this ticket (would prefer people to collaborate than reinventing the wheel).
OT: It would be very cool if podman won't be broken every second day in Rawhide since I'm using it a lot and it breaks very often (seems that gating is not really working).
Last time I checked packit, it said something along the lines of sending a PR to dist-git which would then require a human to hit merge. That didn't sound like fun to me. Have things changed to the point where I can set it and forget about it for the most part?
@santiago is working on resolving the gating tests.
APPROVED (+4, 1, -0)
Metadata Update from @churchyard: - Issue tagged with: pending announcement
I've sponsored @rhcontainerbot to the packager group.
Metadata Update from @psabata: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.