I’m trying something new. There should now be a “continuous” tag which will get the macOS, Windows, AppImage, etc. builds all together.
Right now, for example, it’s marked with the date, time, and commit hash for that particular build:
Automated build on 2025-10-29 20:03 UTC from b9c24ab
I’m sure there will be a few hiccups in this, but it should make it easier to retire the “nightly” links which are always a little unclear on what build they represent.
Looks like this is working. I welcome any feedback about filenames (e.g., @Thomas - you wanted something more descriptive than the previously nightly builds)
The pattern in the name: much better. Minor difference in the approach taken vs the one potentially easier to grasp is that the releases of the Avogadro2 executables as part of avogadrolibs
rather of avogadroapp. So far, I understood avogadrolibs represent a large set of tools to be assembled with fragments, molecules etc. to build the bigger application. Leaving the concept of nightly builds then might require an adjustment of the links like https://nightly.link/OpenChemistry/avogadrolibs/workflows/build_linux/master/Avogadro2-x86_64.AppImage.zip on the avogadroapp landing page, section Installing, too.
They’ll be synced to avogadroapp too. But most of the changes happen in avogadrolibs, so it’d need an actual timed nightly build on avogadroapp to make sure it stays relatively recent.
Conceptual doodle: a GitHub action in avogadroapps is launched by a cron schedule once each two weeks, then checks if the current commit hash in avogadrolibs changed since the last visit. In case change(commit hash) == TRUE, building of a new executable in avogadroapp will start. Or the delta between two visits is a monthly digest (which [for me] would be very much acceptable, too).
