summaryrefslogtreecommitdiffstats
path: root/docs/submodules/storperf
diff options
context:
space:
mode:
authorAric Gardner <agardner@linuxfoundation.org>2017-12-20 12:37:38 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-12-20 12:37:38 +0000
commit7f51f2c3fd093234fe55eca7941f2804082ce843 (patch)
tree9c7b5114ba27050e7323d80fd61cb366ba982f53 /docs/submodules/storperf
parent4f94bf7566a34d9274d460cfe84231cd0bc956ce (diff)
Update git submodules
* Update docs/submodules/releng from branch 'master' - Merge "jjb: xci: xci-verify-jobs: Do not trigger on forbidden paths" - 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>
Diffstat (limited to 'docs/submodules/storperf')
0 files changed, 0 insertions, 0 deletions