Parameterize nightly script and remove user dir dependency#8047
Parameterize nightly script and remove user dir dependency#8047hickeng merged 1 commit intovmware:masterfrom
Conversation
| ESX_67_VERSION="ob-8169922" | ||
| VC_67_VERSION="ob-8217866" | ||
|
|
||
| DEFAULT_TESTCASES="tests/manual-test-cases/Group5-Functional-Tests tests/manual-test-cases/Group13-vMotion tests/manual-test-cases/Group21-Registries tests/manual-test-cases/Group23-Future-Tests" |
There was a problem hiding this comment.
This was just moved from below - need to figure out if:
a. it's actually the full set of tests we should be running
b. why we don't have a nimbus-test-cases directory or similar for those expected to be run automatically
tests/nightly/jenkins-nightly-run.sh
Outdated
| fi | ||
| target="$1" | ||
| echo "Target cluster: "$target | ||
| echo "Target cluster: ${target}" |
There was a problem hiding this comment.
This phrasing is terrible - this isn't a target cluster it's a vSphere version.
tests/resources/Nimbus-Util.robot
Outdated
|
|
||
| :FOR ${IDX} IN RANGE 1 5 | ||
| \ ${out}= Execute Command ${NIMBUS_LOCATION} nimbus-testbeddeploy --lease 0.25 ${testbed} | ||
| \ ${out}= Execute Command ${NIMBUS_LOCATION} nimbus-testbeddeploy --lease 0.25 --testbedSpecRubyFile ./%{BUILD_TAG}/testbeds/${spec} ${args} |
There was a problem hiding this comment.
Only include the spec arguments if a spec was provided.
There was a problem hiding this comment.
Instead I've included a default. This should be revisted based on
vic/tests/resources/Nimbus-Util.robot
Line 254 in e9345d6
| ${out}= Execute Command ${NIMBUS_LOCATION} rm -rf public_html/pxe/* %{BUILD_TAG}/testbeds | ||
| Close connection | ||
|
|
||
| Nimbus Cleanup |
There was a problem hiding this comment.
Add cleanup for BUILD_TAG directory
| @@ -16,84 +16,75 @@ | |||
| ESX_60_VERSION="ob-5251623" | |||
There was a problem hiding this comment.
Add script usage doc.
db59c4e to
19a6d5f
Compare
19a6d5f to
5e836fb
Compare
62d546a to
d246d2e
Compare
This parameterizes the nightly job runner script so that we can pass in the configuration elements that were previously hard coded. The primary difference is it's possible to run a user specified subset of the test cases. Also removes references in the test definitions to specific user directories. There is a mostly duplicated version of the job runner files called jenkins-drs-disabled-run.sh - as best I can determine these files are not unified only because some of the nightly tests have not been confirmed to work when the test executor is in a container.
d246d2e to
3a87280
Compare
This is a follow on from #8047 and corrects the variable quoting when passing though one script to another. This has been tested via a branch build with multiple test suites specified.
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by that work. In the case of the hetrogeneous and NFS tests, it is test updates necessitated by the prior Nimbus-Util.robot updates. In the case of the VSAN tests it is addressing removal of a non-existent path and switching to use the related testbed spec.
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by that work. In the case of the hetrogeneous and NFS tests, it is test updates necessitated by the prior Nimbus-Util.robot updates. In the case of the VSAN tests it is addressing removal of a non-existent path and switching to use the related testbed spec.
This builds on #8047 and #8063 to address some outstanding issues left by that work. In the case of the hetrogeneous and NFS tests, it is test updates necessitated by the prior Nimbus-Util.robot updates. In the case of the VSAN tests it switches to using a testbed descriptor based off the vic-simple-cluster spec instead of what appeared to be a library spec, testng/testbeds/vsan.rb. This disables the complex vSAN testsuite at this time as I could not infer what the complex case was testing, and it is not in the test doc. It's possible that it's testing multiple vSAN datastores and our ability to use either but that's pure speculation.
This parameterizes the nightly job runner script so that we can pass in the configuration elements that were previously hard coded. The primary difference is it's possible to run a user specified subset of the test cases. Also removes references in the test definitions to specific user directories. There is a mostly duplicated version of the job runner files called jenkins-drs-disabled-run.sh - as best I can determine these files are not unified only because some of the nightly tests have not been confirmed to work when the test executor is in a container. (cherry picked from commit 3b269fa)
This is a follow on from vmware#8047 and corrects the variable quoting when passing though one script to another. This has been tested via a branch build with multiple test suites specified. (cherry picked from commit 88d047f)
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by that work. In the case of the hetrogeneous and NFS tests, it is test updates necessitated by the prior Nimbus-Util.robot updates. In the case of the VSAN tests it switches to using a testbed descriptor based off the vic-simple-cluster spec instead of what appeared to be a library spec, testng/testbeds/vsan.rb. This disables the complex vSAN testsuite at this time as I could not infer what the complex case was testing, and it is not in the test doc. It's possible that it's testing multiple vSAN datastores and our ability to use either but that's pure speculation. (cherry picked from commit d533414)
This parameterizes the nightly job runner script so that we can pass in the configuration elements that were previously hard coded. The primary difference is it's possible to run a user specified subset of the test cases. Also removes references in the test definitions to specific user directories. There is a mostly duplicated version of the job runner files called jenkins-drs-disabled-run.sh - as best I can determine these files are not unified only because some of the nightly tests have not been confirmed to work when the test executor is in a container. (cherry picked from commit 3b269fa)
This is a follow on from vmware#8047 and corrects the variable quoting when passing though one script to another. This has been tested via a branch build with multiple test suites specified. (cherry picked from commit 88d047f)
This builds on vmware#8047 and vmware#8063 to address some outstanding issues left by that work. In the case of the hetrogeneous and NFS tests, it is test updates necessitated by the prior Nimbus-Util.robot updates. In the case of the VSAN tests it switches to using a testbed descriptor based off the vic-simple-cluster spec instead of what appeared to be a library spec, testng/testbeds/vsan.rb. This disables the complex vSAN testsuite at this time as I could not infer what the complex case was testing, and it is not in the test doc. It's possible that it's testing multiple vSAN datastores and our ability to use either but that's pure speculation. (cherry picked from commit d533414)
This parameterizes the nightly job runner script so that we can pass in the configuration elements that were previously hard coded. The primary difference is it's possible to run a user specified subset of the test cases. Also removes references in the test definitions to specific user directories. There is a mostly duplicated version of the job runner files called jenkins-drs-disabled-run.sh - as best I can determine these files are not unified only because some of the nightly tests have not been confirmed to work when the test executor is in a container. (cherry picked from commit 3b269fa)
This builds on #8047 and #8063 to address some outstanding issues left by that work. In the case of the hetrogeneous and NFS tests, it is test updates necessitated by the prior Nimbus-Util.robot updates. In the case of the VSAN tests it switches to using a testbed descriptor based off the vic-simple-cluster spec instead of what appeared to be a library spec, testng/testbeds/vsan.rb. This disables the complex vSAN testsuite at this time as I could not infer what the complex case was testing, and it is not in the test doc. It's possible that it's testing multiple vSAN datastores and our ability to use either but that's pure speculation. (cherry picked from commit d533414)
Update the nightly logic to remove all dependence on specific user directories and content.
Update the Jenkins entry point scripts to allow for parameterization and customization of the run.
Of note is the almost complete duplication between the jenkins and upload scripts for drs_disabled and the nightlies. Reaching out to @anchal-agrawal this is because the nightlies were not yet migrated to use a container for running the test executor.
I'm not sure where we will actually go for this given a desire to have the executors be VCH containers themselves. We could have a single image for the job class, an image for the specific jobs, or a general executor image and very task specific images for the job steps. Planning required.