rbm.local.conf.example 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113
  1. ---
  2. ### This file is used to override options from rbm.conf to adapt them
  3. ### to your local setup.
  4. ###
  5. ### Copy this file as rbm.local.conf to enable it, and uncomment the
  6. ### options you want to modify.
  7. ### The tmp_dir option defines where temporary files are stored. The
  8. ### builds are made from this directory, so using a directory on a fast
  9. ### disk can improve build time. By default we are using a tmp directory
  10. ### under the tor-browser-build directory.
  11. #tmp_dir: /tmp
  12. ### The debug option defines whether a debugging shell should be opened
  13. ### automatically in the build directory/container in case of build
  14. ### failure. If you are doing automated builds, you might want to disable
  15. ### this.
  16. #debug: 0
  17. ### The build_log option defines in which file the build logs of each
  18. ### component are stored. If you set it to '-' the logs are output on
  19. ### stdout and stderr.
  20. #build_log: '-'
  21. ### By default, the logs from previous builds are kept in the log files.
  22. ### If you set build_log_append to 0, then previous logs are cleaned
  23. ### when starting a new build.
  24. #build_log_append: 0
  25. buildconf:
  26. buildconf: 1
  27. ### The buildconf/num_procs option can be used to select the number of
  28. ### build processes to run simultaneously. You can also use the
  29. ### RBM_NUM_PROCS environment variable. The default is 4.
  30. #num_procs: 8
  31. ### The buildconf/git_signtag_opt option is useful when you tag a release.
  32. ### It is used to set the 'git tag' argument to select the keyid for
  33. ### signing the tag.
  34. #git_signtag_opt: '-u keyid'
  35. var:
  36. local_conf: 1
  37. ### The var/sign_build option defines if you want to sign the
  38. ### sha256sums-unsigned-build.txt file with gpg.
  39. #sign_build: 1
  40. ### The var/sign_build_gpg_opts option can be used to define some gpg
  41. ### options to select the key to use to sign the sha256sums-unsigned-build.txt
  42. ### file.
  43. #sign_build_gpg_opts: '--local-user XXXXXXXX'
  44. ### The clean configuration is used by the cleaning script to find the
  45. ### branches and build targets you are using, to compute the list of
  46. ### files that should be kept.
  47. ###
  48. ### If you only do alpha builds for all platforms, you can use the
  49. ### following configuration:
  50. #clean:
  51. # HEAD:
  52. # - project: release
  53. # target:
  54. # - alpha
  55. # - torbrowser-all
  56. #
  57. ### If you are doing 'release' builds in the maint-7.0 branch and
  58. ### 'alpha' builds in the master branch, you can use the following
  59. ### configuration:
  60. #clean:
  61. # master:
  62. # - project: release
  63. # target:
  64. # - alpha
  65. # - torbrowser-all
  66. # maint-7.0:
  67. # - project: release
  68. # target:
  69. # - release
  70. # - torbrowser-all
  71. targets:
  72. ### testbuild is based on alpha by default. Uncomment this if you want it
  73. ### to be based on nightly.
  74. #torbrowser-testbuild:
  75. # - testbuild
  76. # - nightly
  77. testbuild:
  78. var:
  79. testbuild: 1
  80. ### Uncomment this if you want to create mar files in your test build.
  81. #build_mar: 1
  82. nightly:
  83. ### By default 'fetch' is set to 1 for nightly builds, meaning that new
  84. ### commits will be fetched automatically during each build. You can
  85. ### disable this during development if you want to do rebuilds to test
  86. ### a specific change, but don't want rebuilds caused by unrelated
  87. ### changes, or if you want to decide at which point new commits are
  88. ### fetched. When 'fetch' is set to 'if_needed', new commits will only
  89. ### be fetched if the selected commit (or branch, or tag) is not present,
  90. ### which means that existing branches won't be updated. In that case
  91. ### you can fetch new commits by running 'make fetch'.
  92. #fetch: 'if_needed'
  93. # vim: filetype=yaml sw=2