summaryrefslogtreecommitdiffstats
path: root/docs/testing/developer/devguide
diff options
context:
space:
mode:
authorMarkos Chandras <mchandras@suse.de>2017-09-28 07:43:34 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-09-28 07:43:34 +0000
commit2034a5bbd497191381a1c40e9d6be2b02f6a31ec (patch)
tree1eb63cd3ad14ad80494564c5e2bb031b5b7750c5 /docs/testing/developer/devguide
parent002409645b45794ac7ee1d4bd3f79cdfdea5a7fd (diff)
Update git submodules
* Update docs/submodules/releng-xci from branch 'master' - Merge changes from topic 'fix-vm-on-jenkins' * changes: xci: scripts: start-new-vm.sh: Fix paths for default XCI test xci: Replace ANSIBLE_VERBOSITY with XCI_ANSIBLE_VERBOSITY xci: scripts: start-new-vm.sh: Print dib output when running on CI xci: scripts: start-new-vm.sh: Use 'unsafe' cache for the clean vm disk xci: xci-deploy.sh: Make sure all local Ansible installations are gone xci: scripts: start-new-vm.sh: Do not allow multiple build-dib-os processes - xci: scripts: start-new-vm.sh: Fix paths for default XCI test The XCI test is located in ~/releng-xci inside the new VM so we need to look there for an existing one or for executing it after the default one has been created and copied to the remote host. Change-Id: Ieb195293da7832bcb5d29c8a28cc3477205f2e5e Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: Replace ANSIBLE_VERBOSITY with XCI_ANSIBLE_VERBOSITY The ANSIBLE_VERBOSITY env variable is actually used internally by Ansible and exporting it actually makes Ansible super verbose even if the variable is empty. This feature is going away in the future so we introduce our own XCI_ANSIBLE_VERBOSITY variable which is simply passed to the command line to control verbosity in a proper and deterministic way. Change-Id: I8a32eeb1a86b4cb0a9872a51bbe9f9624d096e39 Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: scripts: start-new-vm.sh: Print dib output when running on CI Until we are able to fetch the dib images from external resources, we need to build them as part of the job. diskimage-builder can sometimes fail so we need to be able to see the log for debug purposes. Change-Id: Iab8bfba08daa7095cf76537f629c8e7bf6330b17 Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: scripts: start-new-vm.sh: Use 'unsafe' cache for the clean vm disk This is not a production virtual machine and we don't care if we lose data in case it's killed unexpectedly so we can just ignore the 'flush' commands from the guest. This will also improve the overall I/O in the VMs. Change-Id: Ib486a073f667e22f4a1e65a220ac553874f708cc Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: xci-deploy.sh: Make sure all local Ansible installations are gone We need to ensure that all Ansible installations are gone before we install it again so we can ensure that a local or system wide installation will not take precedence over the one we try to install. Change-Id: I9daf66d661697baf63340ba4af1cd58fbd81f143 Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: scripts: start-new-vm.sh: Do not allow multiple build-dib-os processes apt-get is really unhappy when another instance is running and fails with the following error: E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? Change-Id: I2fe343fdab8438cb112cce0a4f81c7e3977c55f9 Signed-off-by: Markos Chandras <mchandras@suse.de>
Diffstat (limited to 'docs/testing/developer/devguide')
0 files changed, 0 insertions, 0 deletions