Configuration for Gadgetbridge F-Droid repository.
Go to file
vanous 61bb817472
ci/woodpecker/push/woodpecker Pipeline is pending Details
Update metadata
2023-10-09 20:23:05 +02:00
repoconfig Update metadata 2023-10-09 20:23:05 +02:00
.woodpecker.yml Update to jdk 17 and BUILD_TOOLS_VERSION=33.0.2 2023-10-08 22:19:40 +02:00
Dockerfile Update to jdk 17 and BUILD_TOOLS_VERSION=33.0.2 2023-10-08 22:19:40 +02:00
LICENSE Initial commit 2022-01-15 18:24:58 +01:00 Update to jdk 17 and BUILD_TOOLS_VERSION=33.0.2 2023-10-08 22:19:40 +02:00

Nightly F-Droid repository for Gadgetbridge

Files in the repoconfig


These files are used by the CI/CD from the nightly-branch of Gadgetbridge.

  • repoconfig/ - prepares changelog for the list of changes in F-Droid client
  • repoconfig/ - creates list of apks and their descriptions on the repo index.html page
  • repoconfig/ - copies apks to the repo config directory
  • repoconfig/ - adds a message to the issue tracker
  • repoconfig/ - used with debug-branch to publish a custom apk as a release to the pages repo
  • repoconfig/ - make clickable url in the console (on woodpecker task output)
  • Dockerfile - definition for the custom docker image that is used in (all) build steps
  • .woodpecker.yml - CI steps to create and publish the Docker image into the Package repository.

Used on a remote server

  • repoconfig/ - this script is run via cron on another server to update the nightly-branch and to approve the CI build.

Unused, kept for the record

  • repoconfig/unused/ -removes the release tag from the releases in pages repo
  • repoconfig/unused/ - creates a new release and uploads apks to the releases in pages repo
  • repoconfig/unused/ and repoconfig/ - Can change index files and re-sign them with the keyfile

Docker image

The Docker image we use is based on cs8898/android-fdroid-sdk:33.0.0 image, it contains Android SDK and fdroid publishing tool, we then add some small utilities needed for f-droid publishing. The image is built by Codeberg's CI (the task must be manually enabled to run) and hosted in this very repo on Codeberg here.

Typically, our image is tagged latest but as there can be caching on Codeberg crossing our path, it is better to tag based on current tools version.

Woodpecker pipeline setup:

Woodpecker secrets

Signing key

This key and passwords are used to sign the repo index files and to sign the nightly apks.

Clone repo fdroid-repo-config, make sure to have fdroidserver installed (python -m pip install fdroidserver==2.1a0), remove the empty key and generate a new one:

Comment the keystorepass and keypass in the config.yml!

git checkout fdroid-repo-config
cd repoconfig
rm keystore.p12
fdroid update --create-key

This generates 3 things: keystore.p12 keyfile, keystorepass and keypass in the config.yml.

Take the key and convert it to base64 for the CI/CD:

cat keystore.p12 | base64 > out

Add the key to Woodpecker as a secret, via woodpecker cli:

/path_to/woodpecker secret add -repository Freeyourgadget/Gadgetbridge -name signing_key -value @out -event push

Also, add the keystorepass and keypass into the Woodpecker secrets as keystorepass and keypass. In reality, these two passwords are the same.

Put the branch back to original state:

git restore .
git clean -f -d

Commit token

Create personal access token and add this token as commit_token to the Woodpecker secrets. The git config to push to the pages and to the nightly-branch repo is set to:

- git config "CODEBERG CI"
- git config "noreply@nodomain.nodomain"


  • currently, we need to keep the nightly setup in an extra branch in order to be able to run "can master build" CI task without always running the "nightly" build and making a release. Also, triggering must happen via external server, as Woodpecker does not support cron tasks yet. We are waiting for these issues and
  • if we wanted to add more apps to the f-droid repo, we would need to re-build them all at the same time - we would need to clone their git repo and copy the apk to fdroid config directory. To do this without rebuilding everything, some other persistent storage would be useful.
  • hosting of the apks must currently be done from the pages git repo. This could over time blow the repo huge in size, this is why each automated commit squashes with the previous commit. This could be an issue in the future. Unfortunately, the other possibility to tell F-Droid client that the apk is hosted elsewhere is not possible, see here, at it also cannot be done via http redirects, see here (actually, from that discussion in am not clear if http redirects now work or not).