You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Michael Pöhn 69e4d48924 Merge branch 'remove-force_build_tools' into 'master' 11 months ago
buildserver provision-apt-get-install: gpg needs to come from stretch-backports 1 year ago
completion scanner: add a simple scan for blacklisted classes after build step 1 year ago
examples remove "force_build_tools" config option, closes #738 11 months ago
fdroidserver remove "force_build_tools" config option, closes #738 11 months ago
hooks hooks: add gradlew-fdroid to BASH_FILES 3 years ago
locale remove dscanner subcommand 2 years ago
tests remove "force_build_tools" config option, closes #738 11 months ago
.gitignore remove last vestige of latestapps.dat 11 months ago
.gitlab-ci.yml fix fedora test 11 months ago
.pylint-rcfile update outdated pylint setup 4 years ago
.travis.yml travis: retry `brew install`, it randomly fails on downloads 2 years ago
.weblate add weblate config for wlc CLI tool 2 years ago update changelog: remove txt metadata support 12 months ago
LICENSE Rename COPYING to LICENSE 6 years ago remove obselete tests 1 year ago remove dscanner subcommand 2 years ago
fdroid fix tests on old python version 2 years ago
gradlew-fdroid add gradle 6.6.1 11 months ago
jenkins-build-all jenkins-build-all: enable deploy_process_logs for CI test 2 years ago
jenkins-setup-build-environment jenkins-setup-build-environment: fix my stoopid typo 1 year ago
jenkins-test jenkins-test: remove rewritemeta, it is well covered elsewhere 11 months ago
makebuildserver build-tools 30.0.2 11 months ago
setup.cfg declare LICENSE file in setup.cfg 1 year ago unpin pyasn1_modules 11 months ago

CI Builds fdroidserver buildserver fdroid build --all publishing tools
GNU/Linux fdroidserver status on GNU/Linux buildserver status fdroid build all status fdroid test status
macOS fdroidserver status on macOS

F-Droid Server

Server for F-Droid, the Free Software repository system
for Android.

The F-Droid server tools provide various scripts and tools that are
used to maintain the main
F-Droid application repository. You
can use these same tools to create your own additional or alternative
repository for publishing, or to assist in creating, testing and
submitting metadata to the main repository.

For documentation, please see, or you can
find the source for the documentation in

What is F-Droid?

F-Droid is an installable catalogue of FOSS (Free and Open Source Software)
applications for the Android platform. The client makes it easy to browse,
install, and keep track of updates on your device.


There are many ways to install fdroidserver, they are documented on
the website:

All sorts of other documentation lives there as well.


There are many components to all of the tests for the components in
this git repo. The most commonly used parts of well tested, while
some parts still lack tests. This test suite has built over time a
bit haphazardly, so it is not as clean, organized, or complete as it
could be. We welcome contributions. Before rearchitecting any parts
of it, be sure to contact us to discuss
the changes beforehand.

fdroid commands

The test suite for all of the fdroid commands is in the tests/
subdir. .gitlab-ci.yml and .travis.yml run this test suite on
various configurations.

  • tests/complete-ci-tests runs pylint and all tests on two
    different pyvenvs
  • tests/run-tests runs the whole test suite
  • tests/*.TestCase are individual unit tests for all of the fdroid
    commands, which can be run separately, e.g. ./update.TestCase.

Additional tests for different linux distributions

These tests are also run on various distributions through GitLab CI. This is
only enabled for master@fdroid/fdroidserver because it'll take longer to
complete than the regular CI tests. Most of the time you won't need to worry
about them but sometimes it might make sense to also run them for your merge
request. In that case you need to remove these lines from

and push this to a new branch of your fork.

Alternatively run them

like this: gitlab-runner exec docker ubuntu_lts


The tests for the whole build server setup are entirely separate
because they require at least 200GB of disk space, and 8GB of
RAM. These test scripts are in the root of the project, all starting
with jenkins- since they are run on


Everything can be translated. See
Translation and Localization
for more info.
translation status