ea5f8fea7c
So far, when the scheduler re-enqueued a change that was missing dependencies, it also reported the Github check-run as cancelled but did not report start as the re-enqueued item was added as a "quiet" item. The check-run on Github was still marked as success after the item finished. But until then it appeared as cancelled even if the change was successfully re-enqueued. To fix this we'll not call the dequeue reporters when the change could be re-enqueued. The dequeued item will still be reported to the database though. Change-Id: Iea465ca1d9132322b912f7723e3ae41a8c6d3002
41 lines
764 B
Plaintext
41 lines
764 B
Plaintext
[statsd]
|
|
# note, use 127.0.0.1 rather than localhost to avoid getting ipv6
|
|
# see: https://github.com/jsocol/pystatsd/issues/61
|
|
server=127.0.0.1
|
|
|
|
[scheduler]
|
|
tenant_config=main.yaml
|
|
relative_priority=true
|
|
|
|
[merger]
|
|
git_dir=/tmp/zuul-test/merger-git
|
|
git_user_email=zuul@example.com
|
|
git_user_name=zuul
|
|
|
|
[executor]
|
|
git_dir=/tmp/zuul-test/executor-git
|
|
load_multiplier=100
|
|
|
|
[connection gerrit]
|
|
driver=gerrit
|
|
server=review.example.com
|
|
user=jenkins
|
|
sshkey=fake_id_rsa_path
|
|
password=badpassword
|
|
|
|
[connection github]
|
|
driver=github
|
|
webhook_token=0000000000000000000000000000000000000000
|
|
app_id=1
|
|
app_key=$APP_KEY_FIXTURE$
|
|
|
|
[connection smtp]
|
|
driver=smtp
|
|
server=localhost
|
|
port=25
|
|
default_from=zuul@example.com
|
|
default_to=you@example.com
|
|
|
|
[database]
|
|
dburi=$MYSQL_FIXTURE_DBURI$
|