Remove deprecated libtaskotron options
This commit is contained in:
parent
f8fecc2d42
commit
b300339ee5
1 changed files with 0 additions and 19 deletions
|
@ -51,17 +51,6 @@ buildbot_task_step: 'runtask'
|
|||
## This section controls which result reports you want to send after the test
|
||||
## execution is complete.
|
||||
|
||||
## Overall setting whether to send any reports at all. If this is False, no
|
||||
## reports will be sent anywhere, regardless of your configuration for
|
||||
## individual recipient systems.
|
||||
## [default: True for production, False for development]
|
||||
reporting_enabled: True
|
||||
|
||||
## If True, test results (for selected tests) will be sent as comments to
|
||||
## Fedora Update System (Bodhi). This requires that you have Bodhi
|
||||
## credentials filled in secrets.conf. See also 'reporting_enabled' option.
|
||||
report_to_bodhi: {{ client_report_to_bodhi }}
|
||||
|
||||
## Whether to send test results to the configured ResultsDB server. See also
|
||||
## 'reporting_enabled' option.
|
||||
report_to_resultsdb: True
|
||||
|
@ -81,9 +70,6 @@ koji_url: {{ kojihub_url }}
|
|||
## URL of repository of all the RPM packages built in Koji
|
||||
#pkg_url: http://kojipkgs.fedoraproject.org/packages
|
||||
|
||||
## URL of Bodhi instance used for communication about package updates
|
||||
bodhi_server: {{ bodhi_server }}
|
||||
|
||||
## Whether to use staging Bodhi instance instead of production (the
|
||||
## default one).
|
||||
#bodhi_staging: False
|
||||
|
@ -179,11 +165,6 @@ log_level_stream: INFO
|
|||
## All login credentials and other secrets are here. If you add some secret
|
||||
## here, make sure you make this file readable just for the right user accounts.
|
||||
|
||||
## FAS (Fedora Accounts System) credentials
|
||||
## These credentials are used when reporting results into Bodhi.
|
||||
fas_username: '{{ taskotron_fas_user }}'
|
||||
fas_password: '{{ taskotron_fas_password}}'
|
||||
|
||||
## SSH private key location. Used for remote task execution, when connecting to
|
||||
## VMs and remote machines. If your systems are not configured for automatic
|
||||
## connection (private keys located in SSH's standard search path), specify a
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue