jjb: xci: xci-verify-jobs: Do not trigger on forbidden paths

We should set 'disable-strict-forbidden-file-verification' to 'false'
to really prevent any changes to the forbidden paths to trigger a CI
job. When this option is set to 'True', then a patchset that modifies
both allowed and forbidden paths will trigger a job. However, in order
to be on the same side in regards to the start-new-vm.sh script, we
really shouldn't trigger the job. Moreover, we drop the rest of the
forbidden paths since we can use the 'skip-verify' topic name to
skip the deployment.

Change-Id: I2a89e51861c7fb8541fe774b128ea4049e91df43
Signed-off-by: Markos Chandras <mchandras@suse.de>

diff --git a/jjb/xci/xci-verify-jobs.yml b/jjb/xci/xci-verify-jobs.yml
index 9fa5633..7ca25e4 100644 (file)
--- a/jjb/xci/xci-verify-jobs.yml
+++ b/jjb/xci/xci-verify-jobs.yml
@@ -106,16 +106,8 @@
               branches:
                 - branch-compare-type: 'ANT'
                   branch-pattern: '**/{branch}'
-              disable-strict-forbidden-file-verification: 'true'
+              disable-strict-forbidden-file-verification: 'false'
               forbidden-file-paths:
-                - compare-type: ANT
-                  pattern: 'prototypes/**'
-                - compare-type: ANT
-                  pattern: 'upstream/**'
-                - compare-type: ANT
-                  pattern: '**/README.rst'
-                - compare-type: ANT
-                  pattern: 'docs/**'
                 - compare-type: ANT
                   pattern: 'xci/scripts/vm/**'
           readable-message: true