Tdo you have an example?
Rpodman pull quay.io/fedora/fedora:42@sha256:999c32a870abe038e2694d838d0109f47838fb4f433c7f5597c59853bf0624c8Tworks!
MCan docker do that as well?
MNo. Apparently. Digest only
RThis seems to be working now.
https://github.com/ublue-os/main/pull/792
It may turn out to be a terrible idea, or saturate the builders... If that's the case, it's an easy revert.
https://github.com/ublue-os/main/pull/792
It may turn out to be a terrible idea, or saturate the builders... If that's the case, it's an easy revert.
Tlets see!
Ti hope this works LOL
Tcuz maintaining ublue by just click click click renovate would be amazing
RHow important is it to have the updated images immediately?
Just thinking if Timothee builds F40 and F41 at different times, it may cause duplicated builds (unless we implement the split image-versions files here too).
If we're okay with checking for images every 3 hours or so, that would reduce the duplicated builds while still ensuring we slirp up the new images that day
Just thinking if Timothee builds F40 and F41 at different times, it may cause duplicated builds (unless we implement the split image-versions files here too).
If we're okay with checking for images every 3 hours or so, that would reduce the duplicated builds while still ensuring we slirp up the new images that day
Tthat sounds good to me tbh
RI guess we merge my current PR and see how it goes. Can easily be tweaked later
Jneeds and ack
J@tulip ack it
Thow did you ping me without pinging me?
Jdunno
JI turned off F40 workflow in main
RI really hope this thing works well enough...
RIn theory it's exactly what we wanted, but right now, all I can think about is the things that could go wrong with it
Jhahahaha
Jthe others make way more builds than main
Jthis is a good test
RLast PR for the day
Cleans up Fedora 40 workflows, packages and bash after the workflows have been disabled
https://github.com/ublue-os/main/pull/786
Cleans up Fedora 40 workflows, packages and bash after the workflows have been disabled
https://github.com/ublue-os/main/pull/786
RITS WORKING!
https://github.com/ublue-os/main/pull/799
akmods built 30 minutes ago, and we have an automerging PR to bump the digests
https://github.com/ublue-os/main/pull/799
akmods built 30 minutes ago, and we have an automerging PR to bump the digests
Bso... it's going to generate a renovate PR everytime akmods updates or upstream ostree-desktops? but then it automerges that PR?
RCorrect. The goal is to remove as many useless builds as possible.
So hopefully removing the schedule trigger and relying on these digest bumps, although the schedules are still enabled for now
So hopefully removing the schedule trigger and relying on these digest bumps, although the schedules are still enabled for now
RHappy to revisit if we think this is a good idea after one or two builds
Bit sounds great! I'm happy to see how this goes for a few days
T@j0rge
Tthe automated renovate clickops future is coming soon
RNo click ops... All automated 
Toh wow nice!
RSo we do still have a redundant pull_request trigger build that we could potentially remove if we move tagging to push triggers. This is going back to the tagging to non-prod tags in merge queues and re-tagging them with the prod ones after the merge queue is merged to main
Jhell yeah
Jmy bet is we'll need to shut off the cron because it's timed to go off an hour after akmods builds, so it'll be a race between that and the bot, and if the bot wins the cron fires off anyway.
JBut this is quite exciting
Byeah, this is what i wonder about too
J
JSo we've had an interesting cycle
J
Tthe growth is kinda crazy?
Tlike what do you MEAN
Ti cannot believe how active #
introductions is
introductions is
Tomg yeah! i just noticed that!
Tlike there are new introductions a few hours apart
J
Jconversations are reddit threads, discourse, and discord
J
TT@tryhardsoccermomswag another person since you've said that
