The original trigger appears to have been pulled from a verify job
rather than a merge job. This should fix build-on-merge function.
Change-Id: I77ba8479801a82a5d1d3e670ba8822cb773cfdb9
Signed-off-by: Eric Ball <eball@linuxfoundation.org>
- comment-added-contains-event:
comment-contains-value: remerge$
- comment-added-contains-event:
comment-contains-value: remerge$
+ gerrit_trigger_file_paths:
+ - compare-type: ANT
+ pattern: '**'
+
scm:
- lf-infra-gerrit-scm:
jenkins-ssh-credential: '{jenkins-ssh-credential}'
scm:
- lf-infra-gerrit-scm:
jenkins-ssh-credential: '{jenkins-ssh-credential}'
triggers:
- gerrit:
server-name: '{gerrit-server-name}'
triggers:
- gerrit:
server-name: '{gerrit-server-name}'
- trigger-on:
- - patchset-created-event:
- exclude-drafts: 'false'
- exclude-trivial-rebase: 'false'
- exclude-no-code-change: 'false'
- - change-merged-event
- - comment-added-contains-event:
- comment-contains-value: 'recheck'
- - comment-added-contains-event:
- comment-contains-value: 'reverify'
+ trigger-on: '{obj:gerrit_merge_triggers}'
+ projects:
+ - project-compare-type: ANT
+ project-pattern: '{project}'
+ branches:
+ - branch-compare-type: ANT
+ branch-pattern: '**/{branch}'
+ file-paths: '{obj:gerrit_trigger_file_paths}'
builders:
- lf-infra-pre-build
builders:
- lf-infra-pre-build