From ba18b3c047a317f6d29dd428e6318abe030ad4d5 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Tue, 22 Jul 2014 10:50:51 -0400 Subject: [PATCH] convert to two level recheckwatchbot.yaml As of I7353af4c3f141d4bd617d6fd388d7957e0586ba8 we'll introduce the ability to have a 2 layer config which includes the messages that we'll send back to the user on gerrit outside of the elastic-recheck code base. This makes it easier to make changes to the UX consistent with what we want to change with the rest of the config. Change-Id: I9208123a4cb3be02c272cd8a6eba460f4130a960 Depends-On: I7353af4c3f141d4bd617d6fd388d7957e0586ba8 --- .../files/recheckwatchbot.yaml | 23 ++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/modules/elastic_recheck/files/recheckwatchbot.yaml b/modules/elastic_recheck/files/recheckwatchbot.yaml index dc2f0bdc5f..f8cca1d86d 100644 --- a/modules/elastic_recheck/files/recheckwatchbot.yaml +++ b/modules/elastic_recheck/files/recheckwatchbot.yaml @@ -1,6 +1,27 @@ -openstack-qa: +channels: + openstack-qa: projects: - all events: - positive - negative + +messages: + # | means don't fold newlines, > means do + found_bug: | + I noticed jenkins failed, I think you hit bug(s): + + %(bugs)s + footer: >- + For more details on this and other bugs, please see + http://status.openstack.org/elastic-recheck/ + recheck_instructions: >- + If you believe we've correctly identified the failure, feel free to leave a 'recheck' + comment to run the tests again. + unrecognized: >- + Some of the tests failed in a way that we did not understand. Please help + us classify these issues so that they can be part of Elastic Recheck + http://status.openstack.org/elastic-recheck/ + no_bugs_found: >- + I noticed jenkins failed, refer to: + https://wiki.openstack.org/wiki/GerritJenkinsGithub#Test_Failures