Remove force_build_tools config option Closes #738 See merge request fdroid/fdroidserver!797
|11 months ago|
|buildserver||1 year ago|
|completion||1 year ago|
|examples||11 months ago|
|fdroidserver||11 months ago|
|hooks||3 years ago|
|locale||2 years ago|
|tests||11 months ago|
|.gitignore||11 months ago|
|.gitlab-ci.yml||11 months ago|
|.pylint-rcfile||4 years ago|
|.travis.yml||2 years ago|
|.weblate||2 years ago|
|CHANGELOG.md||12 months ago|
|LICENSE||6 years ago|
|MANIFEST.in||1 year ago|
|README.md||2 years ago|
|fdroid||2 years ago|
|gradlew-fdroid||11 months ago|
|jenkins-build-all||2 years ago|
|jenkins-setup-build-environment||1 year ago|
|jenkins-test||11 months ago|
|makebuildserver||11 months ago|
|setup.cfg||1 year ago|
|setup.py||11 months ago|
|CI Builds||fdroidserver||buildserver||fdroid build --all||publishing tools|
Server for F-Droid, the Free Software repository system
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.
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
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.
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
- tests/complete-ci-tests runs pylint and all tests on two
- tests/run-tests runs the whole test suite
- tests/*.TestCase are individual unit tests for all of the
commands, which can be run separately, e.g.
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
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 https://jenkins.debian.net.
Everything can be translated. See
Translation and Localization
for more info.