|author||Erich Eckner <email@example.com>||2018-05-25 11:16:06 +0200|
|committer||Erich Eckner <firstname.lastname@example.org>||2018-05-25 11:16:06 +0200|
1 files changed, 42 insertions, 18 deletions
@@ -26,32 +26,62 @@ This includes scripts to be run on the build master as well as scripts to be run
-The standard configuration in `conf/default.conf` can be locally overwritten by `conf/local.conf`.
+The standard configuration in `conf/*.conf.example` can be locally overwritten by removing the `.example` prefix, uncommenting the desired variables and changing the values.
### build master only
* add `command=".../bin/slave-build-connect $slave-identifier" $ssh-key` to `~/.ssh/authorized_keys` for each build slave
### build slave only
* set `keyserver-options auto-key-retrieve` in ~/.gnupg/gpg.conf
* put an i686 mirror into `/etc/pacman.d/mirrorlist` as __first__ mirror
+## tools for the build master and the build slaves
+Scan binaries for certain opcodes.
+Clean the packages' git repositories.
+Helper for `check-opcodes`.
+Strict style check for this code base.
## tools for the build master
+Bootstrap the mysql database.
Print some informational statistics.
-Proxy command to be allowed for connection via ssh from build slaves - this way, they can execute exactly the commands they need to operate.
-Calculate how many packages on the build list depend on each package on the build list.
+Receive list of packages with issues from the bug tracker.
+Dump the structure of the database.
Clean up left over files.
+Copy a package into [build-support].
Move around packages on the master mirror.
+Delete obsolete packages on the master mirror.
+Filter content of build-logs for display on the webserver.
+Find packages which are no longer available upstream.
Receive a build assignment from the `build-list`.
Update the `build-list`.
+Answer the irc channel.
+Connect to and watch the irc channel.
Interpret the content of an email - also checks for validity of the mail.
+Modify status of a package in the database.
+Receive ping from slave.
Reorder the build list.
+Step brother of `repo-add` and `repo-remove`.
Return an assignment - either a tar of built package(s) or of error logs.
@@ -60,26 +90,20 @@ Check sanity of build master.
Seed the build list from an upstream mirror or a manual package list.
Generate graphs of dependencies between build-list packages for the web server.
+Proxy command to be allowed for connection via ssh from build slaves - this way, they can execute exactly the commands they need to operate.
Script to investigate why a (desired) action is not done.
+Find which package contains a given file.
## tools for the build slaves
Get a build assignment from the build master, build it and report back.
Remove packages from /var/cache/archbuild32 which do not match their checksum.
+Ping the build master to show the slave is still compiling.
## working directory
-In the standard configuration, the directory `work` will be used to cache the following data:
-* `build-list`, `build-list.loops`, `build-order`, `tsort.error`:
-order of builds of packages and dependency loops
-packages to be deleted
-current revisions of the respective repository
-meta data of packages
-information on build process of packages (lock files, markers for broken packages)
-* `repos/packages`, `repos/community`, `repos/packages32`:
-git repositories of PKGBUILDs and modifications
+In the standard configuration, the directory `work` will be used to cache some volatile data, as well as the git repositories of PKGBUILDs and modifications (in `repos/packages`, `repos/community`, `repos/packages32`).