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>
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"
- branch-compare-type: ANT
branch-pattern: "**/{branch}"
file-paths: "{obj:gerrit_trigger_file_paths}"
+ comment-text-parameter-mode: PLAIN
--- /dev/null
+---
+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.