fdroidserver.schedule_verify module

Schedule packages to build and verify.

This creates a list of Application ID/Version Code that need the verify process to be run.

Since this is an internal command, the strings are not localized.

fdroidserver.schedule_verify.get_scheduled(versions)

Get versions that need to be built and there is local build metadata for it.

fdroidserver.schedule_verify.get_versions(repo='https://f-droid.org/repo?fingerprint=43238D512C1E5EB2D6569F4A3AFBF5523418B82E0A3ED1552770ABB9A9C9CCAB')

Get the list of versions that need to be built, newest first.

Newest are built first because older versions that are still not built are most likely to be failing builds. Repeating failed builds mostly results in another failure.

If there are versions with the same versionCode but different signers, there will still only be a single entry returned. If the rebuild matches one signature, that is enough.

fdroidserver.schedule_verify.main()

fdroidserver.schedule_verify.sendchange(scheduled, verbose=False)

Use buildbot sendchange to submit builds to the queue.

This requires the automatically generated password to authenticate to the buildbot instance, which is created at a static path by the buildbot master: https://gitlab.com/fdroid/buildbot/-/merge_requests/1

The passwd file’s path is hardcoded in the server setup, which is defined outside of fdroidserver. Think of the path as a variable name for accessing a value from the filesystem.