diff options
| author |   Aric Gardner <agardner@linuxfoundation.org> | 2017-12-20 12:37:38 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@opnfv.org> | 2017-12-20 12:37:38 +0000 |
| commit | 39f1ba6dd61c0eaffb4bad05494a358357b40fa7 (patch) | |
| tree | b9c54dbe8f001d9c659fa1e71b589305b828dabe /docs/development/opnfvsecguide/introduction.rst | |
| parent | 13be3e8e27db0cff70f8529733a68cb22da11f72 (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/development/opnfvsecguide/introduction.rst')
0 files changed, 0 insertions, 0 deletions