test/build_files/buildbot/README.md

Buildbot Configuration
=====================

Files used by Buildbot's `compile-code` step.
Update all README to clearify intention or usage Add snap configuration file used by Buildbot snap store steps1 2021-05-31 18:58:42 +02:00			`Buildbot Configuration`
			`=====================`
Initial implementation of code signing routines This changes integrates code signing steps into a buildbot worker process. The configuration requires having a separate machine running with a shared folder access between the signing machine and worker machine. Actual signing is happening as a "POST-INSTALL" script run by CMake, which allows to sign any binary which ends up in the final bundle. Additionally, such way allows to avoid signing binaries in the build folder (if we were signing as a built process, which iwas another alternative). Such complexity is needed on platforms which are using CPack to generate final bundle: CPack runs INSTALL target into its own location, so it is useless to run signing on a folder which is considered INSTALL by the buildbot worker. There is a signing script which can be used as a standalone tool, making it possible to hook up signing for macOS's bundler. There is a dummy Linux signer implementation, which can be activated by returning True from mock_codesign in linux_code_signer.py. Main purpose of this signer is to give an ability to develop the scripts on Linux environment, without going to Windows VM. The code is based on D6036 from Nathan Letwory. Differential Revision: https://developer.blender.org/D6216 2019-11-07 16:50:31 +01:00
Update all README to clearify intention or usage Add snap configuration file used by Buildbot snap store steps1 2021-05-31 18:58:42 +02:00			Files used by Buildbot's `compile-code` step.