Review koschei SOP
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
parent
11c1fc3e55
commit
5a42d63c77
2 changed files with 12 additions and 10 deletions
|
@ -4,8 +4,10 @@ Koschei is a continuous integration system for RPM packages. Koschei
|
|||
runs package scratch builds after dependency change or after time elapse
|
||||
and reports package buildability status to interested parties.
|
||||
|
||||
Production instance: https://apps.fedoraproject.org/koschei Staging
|
||||
instance: https://apps.stg.fedoraproject.org/koschei
|
||||
Production instance::
|
||||
https://apps.fedoraproject.org/koschei
|
||||
Staginginstance::
|
||||
https://apps.stg.fedoraproject.org/koschei
|
||||
|
||||
== Contact Information
|
||||
|
||||
|
@ -71,8 +73,8 @@ happens automatically when using the playbook.
|
|||
|
||||
== Disk usage
|
||||
|
||||
Koschei doesn't keep on disk anything that couldn't be recreated easily
|
||||
- all important data is stored in PostgreSQL database, configuration is
|
||||
Koschei doesn't keep on disk anything that couldn't be recreated easily -
|
||||
all important data is stored in PostgreSQL database, configuration is
|
||||
managed by Ansible, code installed by RPM and so on.
|
||||
|
||||
To speed up operation and reduce load on external servers, Koschei
|
||||
|
@ -109,7 +111,7 @@ Koschei services are systemd units managed through `systemctl`. They can
|
|||
be started and stopped independently in any order. The frontend is run
|
||||
using httpd.
|
||||
|
||||
== Suspespending koschei operation
|
||||
== Suspending koschei operation
|
||||
|
||||
For stopping builds from being scheduled, stopping the
|
||||
`koschei-scheduler` service is enough. For planned Koji outages, it's
|
||||
|
@ -163,14 +165,14 @@ koschei-admin clear-notice
|
|||
|
||||
Packages can be added to one or more group.
|
||||
|
||||
To add new group named "mynewgroup", run as koschei user:
|
||||
To add new group named `mynewgroup`, run as `koschei` user:
|
||||
|
||||
....
|
||||
koschei-admin add-group mynewgroup
|
||||
....
|
||||
|
||||
To add new group named "mynewgroup" and populate it with some packages,
|
||||
run as koschei user:
|
||||
To add new group named `mynewgroup` and populate it with some packages,
|
||||
run as `koschei` user:
|
||||
|
||||
....
|
||||
koschei-admin add-group mynewgroup pkg1 pkg2 pkg3
|
||||
|
@ -183,7 +185,7 @@ priority. Any user can change manual priority, which is reset after
|
|||
package is rebuilt. Admins can additionally set static priority, which
|
||||
is not affected by package rebuilds.
|
||||
|
||||
To set static priority of package "foo" to value "100", run as koschei
|
||||
To set static priority of package `foo` to value `100`, run as `koschei`
|
||||
user:
|
||||
|
||||
....
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue