Only creating image if upstream changes occur nightly

[Danathar]

I wasn't able to find a specific feature request for this issue. If someone knows of one, I'd greatly appreciate being pointed to it!

So, I just made my first Bluebuild, very cool!

One thing I’ve noticed: with nightly builds in my Bluebuild action, my custom aurora-dx image is detected and staged as a new image every time I run ujust update, even if neither my recipe nor the upstream base image has changed.

Couldn't the workflow or script be updated so that it only builds a new image if there are upstream changes detected? I like the idea of having a nightly check to catch emergency fixes, but I’d prefer that my system doesn't stage a new image for upgrade every single night when nothing has actually changed because the nightly build made an identical image but with the hash changed (I guess because metadata has changed (date time stamp or something)

For now, my workaround is to change the build schedule, since Aurora updates are usually released once a week early Sunday morning, I’ve set my build to run at noon on Sundays instead.

thanks!

[xynydev]

Many images are built daily to get the latest version of all packages every day. If you want updates less often, you can change the build schedule, as you and Aurora have done. I'm not currently aware of a good way to poll upstream images for updates, and I do not find it all that necessary.

It would be most useful in a situation where you have limited CI/CD resources that you want to conserve, your base image is one that updates with a slow cadence, but you occasionally need to get updates quicker than usual to get some post-release security or usability fixes. If you happen to be in that situation, it should be pretty easy to update your CI/CD workflow to check whether the latest version of the base image you are using matches some persistently stored checksum of the last base image your image is built on, and only rebuild if they don't match.

[Danathar]

thanks!