From 28b83ad2118196588ce52727873419cbbc3c0538 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Jun 17 2019 07:14:48 +0000 Subject: doc: broken indent in brainstorming.rst /home/praiskup/rh/projects/copr/copr/doc/brainstorming.rst:50: WARNING: Unexpected indentation. --- diff --git a/doc/brainstorming.rst b/doc/brainstorming.rst index 9f8f8ad..0021783 100644 --- a/doc/brainstorming.rst +++ b/doc/brainstorming.rst @@ -45,13 +45,14 @@ Backend * determine if it is properly checking the timeout from a dead instance * maybe dump out the PID of the worker that is running so we know which one to kill? -(Done) +Done +^^^^ * have jobs as static records in redis, drop workers for each build and only have process checking build status and downloading results in the end - - advantage is that you don't lose the already done work on builds that were running when copr-be is restarted (which happens on upgrades or a component failure) - - disadvantage is that it includes quite some changes: keeping and maintaining jobs and their states + process with infinite loop that checkes status of the running jobs - - you also need to run the mockchain job on background with stdin and stoud disattached so that it does not halt on SIGHUP - - includes implementation of a nice way to check whether build is finished or not (e.g. check running processes for mockbuilder user could be ok) - - looks like all of this requires some `copr-builder` script to be run on builder? Then `copr-builder` and `copr-backend` can have pre-defined API + - advantage is that you don't lose the already done work on builds that were running when copr-be is restarted (which happens on upgrades or a component failure) + - disadvantage is that it includes quite some changes: keeping and maintaining jobs and their states + process with infinite loop that checkes status of the running jobs + - you also need to run the mockchain job on background with stdin and stoud disattached so that it does not halt on SIGHUP + - includes implementation of a nice way to check whether build is finished or not (e.g. check running processes for mockbuilder user could be ok) + - looks like all of this requires some `copr-builder` script to be run on builder? Then `copr-builder` and `copr-backend` can have pre-defined API - $ copr-builder --config /some/config.conf build / --chroot - the config.conf identifies where 'dist-git' and 'frontend' can be found to do `git clone PKG` and `copr-cli mock-config` - outputs could look like /copr-builder/live-log (stdout + stderr), /copr-builder/results/, /copr-builder/build.running (status)