jenkins-job-builder/tests/triggers/fixtures/gerrit008.yaml
Reinhard Tartler 440acd0fa1 Add support for disable-strict-forbidden-file-verification
Enabling this option will allow an event to trigger a build if the event
contains BOTH one or more wanted file paths AND one or more forbidden
file paths.  In other words, with this option, the build will not get
triggered if the change contains only forbidden files, otherwise it will
get triggered.

Support for this was added in Plugin Version 2.16.0.

Change-Id: I860b076c2393909012c3ac9821559c9e8c9f7e28
2016-03-10 04:44:21 +00:00

44 lines
1.3 KiB
YAML

triggers:
- gerrit:
trigger-on:
- patchset-created-event:
exclude-drafts: true
exclude-trivial-rebase: true
exclude-no-code-change: true
- comment-added-event:
approval-category: 'APRV'
approval-value: 1
projects:
- project-compare-type: 'PLAIN'
project-pattern: 'test-project'
branches:
- branch-compare-type: 'PLAIN'
branch-pattern: 'master'
- branch-compare-type: 'PLAIN'
branch-pattern: 'stable'
file-paths:
- pattern: '**'
forbidden-file-paths:
- compare-type: ANT
pattern: subdirectory/**
disable-strict-forbidden-file-verification: true
topics:
- compare-type: ANT
pattern: refactor-xy**
skip-vote:
successful: true
failed: true
unstable: true
notbuilt: true
silent: false
silent-start: true
escape-quotes: false
no-name-and-email: false
dependency-jobs: 'job1, job2'
notification-level: ALL
dynamic-trigger-enabled: true
dynamic-trigger-url: http://myhost/mytrigger
trigger-for-unreviewed-patches: true
server-name: my-server
failure-message-file: path/to/filename