Explicity set Gerrit comment mode to PLAIN 22/64622/2
authorThanh Ha <zxiiro@gmail.com>
Thu, 23 Jul 2020 19:27:17 +0000 (15:27 -0400)
committerThanh Ha <zxiiro@gmail.com>
Thu, 23 Jul 2020 19:49:35 +0000 (15:49 -0400)
The default setting for this config is BASE64 where it used to be
PLAIN. Explicity set what we expect the mode to be so that the
job does not fail to parse an unexpected base64 string.

Change-Id: Icf8ae74089f6f60cc03f41d4526d038c78e65606
Signed-off-by: Thanh Ha <zxiiro@gmail.com>
jjb/lf-ci-jobs.yaml
jjb/lf-maven-jobs.yaml
releasenotes/notes/jjb-35-gerrit-trigger-0c0e1421c7b4b3be.yaml [new file with mode: 0644]

index a48f325..fd46329 100644 (file)
               branches:
                 - branch-compare-type: ANT
                   branch-pattern: "**/{branch}"
+          comment-text-parameter-mode: PLAIN
 
     builders:
       - shell: !include-raw-escape: ../shell/gerrit-branch-lock.sh
             failed: true
             unstable: true
             notbuilt: true
+          comment-text-parameter-mode: PLAIN
 
 - job-template:
     name: "{project-name}-jjb-deploy-job"
index 77f34de..d13bb5d 100644 (file)
                 - branch-compare-type: ANT
                   branch-pattern: "**/{branch}"
               file-paths: "{obj:gerrit_trigger_file_paths}"
+          comment-text-parameter-mode: PLAIN
diff --git a/releasenotes/notes/jjb-35-gerrit-trigger-0c0e1421c7b4b3be.yaml b/releasenotes/notes/jjb-35-gerrit-trigger-0c0e1421c7b4b3be.yaml
new file mode 100644 (file)
index 0000000..0b50379
--- /dev/null
@@ -0,0 +1,13 @@
+---
+fixes:
+  - |
+    Retains the expected behaviour of Gerrit Trigger job configuration
+    for the comment-event-parameter-mode when a project upgrades their
+    JJB to 3.5.0 or newer.
+
+    In JJB 3.5.0 support was added to configure the
+    comment-event-parameter-mode however, while it's default mode in JJB
+    matches the documented help text for the configuration in Jenkins the
+    Gerrit Trigger plugin itself appears to default to PLAIN mode when
+    the parameter is excluded. This patch retains what we expect to be the
+    default behaviour.