diff options
author | Markos Chandras <mchandras@suse.de> | 2018-04-27 20:21:46 +0100 |
---|---|---|
committer | Gerrit Code Review <gerrit@opnfv.org> | 2018-05-03 12:08:48 +0000 |
commit | 595e4b04762e48598ca632e10f917569756b3340 (patch) | |
tree | 0e3cca9d1665186aefdbe2c9a8ebbfef2d448d84 /docs/index.rst | |
parent | c457e2f2a681e1acbd759720ea85c3b957ff6556 (diff) |
Update git submodules
* Update docs/submodules/releng-xci from branch 'master'
- xci: Improve scenario bootstrapping process
It's best to check whether the scenario/distro/flavor combination is
supported before spending time cloning all the scenarios. Moreover,
we can record the scenario information as a local fact so we can use
it during the deployment later on.
Change-Id: I1971444c6c6302a844f44ea651ad3b83c4da435c
Signed-off-by: Markos Chandras <mchandras@suse.de>
- xci: playbooks: Simplify scenario overrides mechanism
Now that releng-xci does not have any internal scenarios anymore, we can
simplify the way we plug scenarios to XCI. We keep cloning scenarios in
the cache directory but we also allow users to pass a special
'xci_scenarios_overrides' variable similar to the
'opnfv_scenario_requirements.yml' file to allow them to override
specific keys of the dictionaries. This can be used by Jenkins to test
incoming changes by altering the defaults values. For example, when
we want to test a Gerrit change we can create a file called foobar.yml
with the following contents
xci_scenarios_overrides:
- scenario: os-odl-sfc
version: 9fa5400012e02408b416eb7bd26307e7d179abce
refspec: refs/changes/79/55879/7
and load it using
XCI_ANSIBLE_PARAMS="-e @foobar.yml"
This will make XCI checkout the refspec that we want instead of the
default version.
Change-Id: Ida49910b4c79b843582ddd70c00063fe9bc90dd4
Signed-off-by: Markos Chandras <mchandras@suse.de>
Diffstat (limited to 'docs/index.rst')
0 files changed, 0 insertions, 0 deletions