kojira no_repo_effective_age setting
This commit is contained in:
parent
9aab5d5bde
commit
b5950bb209
2 changed files with 12 additions and 3 deletions
|
|
@ -89,7 +89,7 @@ especially in relation to throttling in creating ``newRepo`` tasks.
|
|||
Note that you need to have your database set to use UTC, as otherwise
|
||||
you can end with weird behaviour. For details see
|
||||
https://pagure.io/koji/issue/2159
|
||||
|
||||
|
||||
``queue_file = None``
|
||||
Writable path could be set here. In such case, kojira will write a
|
||||
list of currently monitored tags there with simple statistics in
|
||||
|
|
@ -97,6 +97,12 @@ especially in relation to throttling in creating ``newRepo`` tasks.
|
|||
tags are expired and what is the computed score for them. This can
|
||||
be used to debug and check in realtime the actual performance.
|
||||
|
||||
``no_repo_effective_age = 2 days (172800)``
|
||||
When prioritizing repo regens, the age of the expired repo is the primary
|
||||
factor. This value (measured in seconds) is used when there is no expired
|
||||
repo (e.g. for a new build tag).
|
||||
|
||||
|
||||
Garbage Collector
|
||||
-----------------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue