1. 16 Sep, 2020 1 commit
    • Hans-Christoph Steiner's avatar
      remove "force_build_tools" config option, closes #738 · 08f72465
      Hans-Christoph Steiner authored
      The `force_build_tools` config option was added a long time ago to
      brute force the _build-tools_ version by trying to replace the value
      in `build.gradle` files. This is never something that should be used
      in production, since the app's build metadata should specify this kind
      of thing. And now that we're moving towards _androguard_ for
      everything except fdroid build and fdroid publish, _build-tools_ will
      no longer even be used in the other commands.
      08f72465
  2. 09 Sep, 2020 1 commit
  3. 15 Jun, 2020 1 commit
  4. 10 Jun, 2020 1 commit
  5. 29 May, 2020 1 commit
  6. 14 May, 2020 1 commit
  7. 19 Feb, 2020 1 commit
  8. 15 Jan, 2020 3 commits
  9. 14 Jan, 2020 1 commit
  10. 08 Jan, 2020 1 commit
  11. 16 Dec, 2019 1 commit
  12. 02 Oct, 2019 1 commit
  13. 31 Jul, 2019 1 commit
  14. 06 Jul, 2019 1 commit
  15. 30 Mar, 2019 1 commit
  16. 20 Feb, 2019 1 commit
  17. 19 Jan, 2019 1 commit
  18. 22 Oct, 2018 1 commit
  19. 17 Aug, 2018 2 commits
  20. 12 Aug, 2018 1 commit
  21. 11 Jul, 2018 1 commit
    • Marcus's avatar
      build: improve gradle experience · 9889a98d
      Marcus authored
      This expands the gradle wrapper shell script used by the buildserver for
      usage outside the buildserver environment. It also allows downloading
      whitelisted versions of gradle if they are not yet deployed to the
      buildserver by simply upsating the copy of fdroidserver (in contrast to
      having to reprovision the whole buildserver).
      
      We first move the buildserver/gradle shell script to the repo root
      as gradlew-fdroid, as it's an fdroid specific gradle wrapper.
      We also now sync it inside the build VM before each build.
      
      We then add a list of whitelisted gradle distributions taken from the
      makebuildserver script.
      
      The script additionally now reads two env vars which tell it where to
      expect installed versions of gradle and where it might store downloaded
      gradle .zip files. Both of those are configurable from config.py. As the
      first should normally just be a subdir of the second it's not exposed in
      the example config.py but only used by the buildserver config.py.
      
      Default config now uses this internal gradle wrapper but a path to a
      custom wrapper or specific gradle distribution can still be set from
      config.py.
      
      Closes #98
      Ref: #370
      9889a98d
  22. 27 Jun, 2018 1 commit
  23. 26 Jun, 2018 1 commit
  24. 19 Jun, 2018 3 commits
  25. 12 Mar, 2018 1 commit
    • Gio's avatar
      Fix misleading java_path example · 87fdca0d
      Gio authored
      As you can see in fdroidserver/common.py:219
      for java_version in ('7', '8', '9'):
      the code look for java version without the 1. in front, after getting a
      bunch of error message that JDK could't be found, investigating the code
      and documentation I discovered my configuration was ignored because of
      this and realized the example was wrong
      87fdca0d
  26. 12 Feb, 2018 1 commit
  27. 11 Feb, 2018 1 commit
  28. 23 Jan, 2018 1 commit
  29. 29 Nov, 2017 1 commit
  30. 26 Nov, 2017 1 commit
  31. 11 Aug, 2017 1 commit
  32. 04 Jul, 2017 2 commits
  33. 03 Jul, 2017 1 commit
  34. 24 Apr, 2017 1 commit