RTD Merge job GTriggers should be overridable 37/6537/1
authorThanh Ha <thanh.ha@linuxfoundation.org>
Sun, 17 Sep 2017 04:32:10 +0000 (00:32 -0400)
committerThanh Ha <thanh.ha@linuxfoundation.org>
Tue, 19 Sep 2017 17:02:44 +0000 (13:02 -0400)
Change-Id: I2193129790709c2232ebcd283e25cca8efb978e3
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
jjb/lf-rtd-jobs.yaml

index ad1e6af..5461ae8 100644 (file)
     #     :project-pattern: Project to trigger build against. (default: **)
     #     :stream: Keyword that can be used to represent a release code-name.
     #         Often the same as the branch. (default: master)
+    #
+    #     :gerrit_merge_triggers: Override Gerrit Triggers.
+    #     :gerrit_trigger_file_paths: Override file paths which can be used to
+    #         filter which file modifications will trigger a build.
+    #         (default: - compare-type: ANT
+    #                     pattern: '**/*.rst'
+    #                   - compare-type: ANT
+    #                     pattern: '**/conf.py')
 
     ######################
     # Default parameters #
     stream: master
     submodule-recursive: true
 
+    gerrit_merge_triggers:
+      - change-merged-event
+      - comment-added-contains-event:
+          comment-contains-value: remerge$
+
     #####################
     # Job Configuration #
     #####################
     triggers:
       - gerrit:
           server-name: '{gerrit-server-name}'
-          trigger-on:
-            - change-merged-event
-            - comment-added-contains-event:
-                comment-contains-value: 'remerge$'
+          trigger-on: '{obj:gerrit_merge_triggers}'
           projects:
             - project-compare-type: 'ANT'
               project-pattern: '{project-pattern}'