monitor-gating: Define some more variable in runner.cfg for staging
These variables are used by monitor-gating to slow down its run frequency when an issue is causing problems and to report that a run failed when it did fail. Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
This commit is contained in:
parent
6c2449886c
commit
c3f0b55d47
1 changed files with 13 additions and 0 deletions
|
@ -26,6 +26,19 @@ workflow_multi_gating_args = "--conf /opt/config/monitor_gating.cfg"
|
|||
# The fedpkg command to call to clean up the dangling side-tags
|
||||
{% if env == 'staging' %}
|
||||
fedpkg = "fedpkg-stage"
|
||||
|
||||
# Project whose issue will slow down the subsequent runs (delay defined
|
||||
# above).
|
||||
pagure_blocking_project = "packager-workflow"
|
||||
# blocker issue tags, issue has to have all of them.
|
||||
blocker_tags = ['packager_workflow_blocker', 'staging']
|
||||
|
||||
# Project against which failed runs report their failure.
|
||||
pagure_report_project = "packager-workflow"
|
||||
pagure_api_token = "{{ monitor_gating_pagure_api_token_workflow_stg }}"
|
||||
env = "staging"
|
||||
|
||||
{% else %}
|
||||
fedpkg = "fedpkg"
|
||||
{% endif %}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue