taler-deployment

Deployment scripts and configuration files
Log | Files | Refs | README

README (2241B)


      1 -- 10 JUNE 2020
      2 
      3 Christian recently removed pip install of buildbot, replaced with debian repo version.
      4 
      5 WebUI does not work with Debian package (issue same as https://bugzilla.redhat.com/show_bug.cgi?id=1557687)
      6 
      7 So `buildbot-master` user performed `pip install` for:
      8 
      9 - buildbot-www
     10 - buildbot-waterfall-view
     11 - buildbot-console-view
     12 - buildbot-grid-view
     13 
     14 This needs to be done again whenever Python is updated (currently we are on Python 3.9).
     15 Also:
     16 
     17 - buildbot.www  (Reason: UI was not coming up and Buck thought this might be a necessary package)
     18 
     19 WebUI Note:  `master.cfg` contains "# Authentication for Web UI." and webUI is configured as the "www" worker.
     20 
     21 
     22 -- PRIOR TO 10 JUNE 2020
     23 
     24 Packages needed to use Buildbot 0.9.x.
     25 
     26 - buildbot
     27 - buildbot-worker
     28 - buildbot-www
     29 - buildbot-waterfall-view
     30 - buildbot-console-view
     31 
     32 ======= From GNUnet BB README ========
     33 
     34 
     35 == Enable CI for a repository
     36 
     37 In order to include a repository in the CI it must
     38 
     39 - be added to the buildmaster configuration and assigned to workers
     40   that can actually build it (ask your admin)
     41 - contain CI tasks in the ".buildmaster" directory.
     42 
     43 == CI/CD Tasks
     44 
     45 When a new commit is pushed, each assigned builder will be tasked to
     46 execute the following scripts from the repository in question, in order, if
     47 they exist:
     48 
     49 0. .buildbot/build.sh
     50 1. .buildbot/install.sh
     51 2. .buildbot/test.sh
     52 3. .buildbot/deploy.sh
     53 
     54 If there is a worker-specific script found prefixed with "<workername>_"
     55 the respective script overrides the "default" script.
     56 Usually, you want the deploy script to only run on a specific worker.
     57 
     58 Example:
     59 
     60 .buildbot/build.sh
     61 .buildbot/install.sh
     62 .buildbot/specialworker_install.sh
     63 .buildbot/deployhost_deploy.sh
     64 
     65 This will result in "build.sh" and "install.sh" to be executed on any worker.
     66 But, "deployhost_deploy.sh" will only be executed on the worker "deployhost".
     67 The worker "specialworker" will not execute "install.sh" but instead
     68 "specialhost_install.sh". This script may omit any installation or modify the
     69 functionality of the standard "install.sh".
     70 
     71 == Custom builds
     72 
     73 Buildbot is very configurable. If you need very specific build configurations
     74 that requires functions only available in the buildmaster configuration,
     75 please contact your admin.