At what point does the build process select the most recent commit/tag for an app?
Does the commit/tag need to exist before the full build process starts (as in, before the first app build is started), or just before the specific app build is started (which can be many hours after the first app build)?
In other words, when one sees the build process has started (in f-droid monitor) is it too late to get a new commit/tag seen by the in process build (and therefore have to wait for the next build)?
There’s a checkupdate CI that finds new Tags (runs daily iirc), and sometimes there’s a checkupdate process running just before the build cycle starts.
If you Tag later there’s no issue… next cycle will get it
The moment a build cycle starts, it grabs the latest version of fdroiddata as it is then. Updates released after that moment will not be part of that build.
So, to be part of a build cycle, you need to have checkupdates notice your update before the cycle starts. checkupdates runs daily, so if you create a tag at least 48 hours before the start of a build cycle you will definitely be in.
If you click that link you will be sent to the GitLab page for fdroiddata and can see what the state is of all the metadata files and thus what is the newest version known by the build cycle.
The wiki shows the build times for each app. I do not see that on monitor. One could click through all the logs linked to by monitor, but I am lazy.
Also, monitor only shows the current (or most recent) build cycle (at least I have not found a way to display old build cycles with monitor - it might be there somewhere). The wiki can show more (notwithstanding a build cycle that hypothetically could have more than 500 entries).
Of course, it is okay if monitor never shows these things. Just a preference of mine that I can easily survive without.