aboutsummaryrefslogtreecommitdiff
path: root/jenkins/bisect.jpl
diff options
context:
space:
mode:
authorGuillaume Tucker <guillaume.tucker@collabora.com>2019-11-12 09:06:32 +0000
committerGuillaume Tucker <guillaume.tucker@collabora.com>2019-11-14 09:12:05 +0000
commit2e586342dea0b3cb3b5d50d83de44faf988459c6 (patch)
treebb16ece3ef893b3d0dd8a2654fab1fd625cf0a18 /jenkins/bisect.jpl
parenta0f795749d0b18743b70daf216f48faffc8d5993 (diff)
bisect.jpl: tweak email subject
Remove the git describe to shorten the email subject and move the test plan name after "bisection:" in preparation for test case bisections. For example, rather than: broonie-sound/for-next boot bisection: v5.4-rc6-292-gc1efaea10be0 on sun8i-h3-libretech-all-h3-cc we would now have: broonie-sound/for-next bisection: boot on sun8i-h3-libretech-all-h3-cc or potentially: broonie-sound/for-next bisection: v4l2-compliance on sun8i-h3-libretech-all-h3-cc The git describe string was also a bit misleading as it's the "bad" kernel revision initially tested, not the one found by the bisection. To better connect this report with the commit it has found, we should make it reply to the original thread when the patch was submitted on a mailing list. Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
Diffstat (limited to 'jenkins/bisect.jpl')
-rw-r--r--jenkins/bisect.jpl4
1 files changed, 3 insertions, 1 deletions
diff --git a/jenkins/bisect.jpl b/jenkins/bisect.jpl
index f8aa3f9..b0eae35 100644
--- a/jenkins/bisect.jpl
+++ b/jenkins/bisect.jpl
@@ -492,7 +492,9 @@ def bisectNext(kdir, status) {
*/
def pushResults(kci_core, kdir, checks, params_summary) {
- def subject = "${params.KERNEL_TREE}/${params.KERNEL_BRANCH} ${params.PLAN} bisection: ${params.KERNEL_NAME} on ${params.TARGET}"
+ def subject = "\
+${params.KERNEL_TREE}/${params.KERNEL_BRANCH} bisection: \
+${params.TEST_PLAN} on ${params.TARGET}"
dir(kci_core) {
withCredentials([string(credentialsId: params.KCI_TOKEN_ID,