Hi all, My name is Karthik. In our company we are planning have our own t_functional testing running and add more tests and contribute back to the community. To start with planning to run test suite in Vagrant VM and got struck in pushing the test suite to Vagrant VM and run the ./runtest.sh I know I can have a "Execute Shell" block in Jenkins with vagrant ssh -c "git clone xxxx" and vagrant ssh -c "./runtests.sh" but it doesn't look the right way to do with Jenkins !! Isn't it ? My blind guess on whats being done in ci.centos is kickstarting machine/provisioning VM, making it as jenkins-slave and running the job on it ?
So can you please advice how test suite is pushed to target Machine/VM ?
Thanks
On Feb 23 23:24, karthik kumar wrote:
Hi all, My name is Karthik. In our company we are planning have our own t_functional testing running and add more tests and contribute back to the community. To start with planning to run test suite in Vagrant VM and got struck in pushing the test suite to Vagrant VM and run the ./runtest.sh I know I can have a "Execute Shell" block in Jenkins with vagrant ssh -c "git clone xxxx" and vagrant ssh -c "./runtests.sh" but it doesn't look the right way to do with Jenkins !! Isn't it ? My blind guess on whats being done in ci.centos is kickstarting machine/provisioning VM, making it as jenkins-slave and running the job on it ?
So can you please advice how test suite is pushed to target Machine/VM ?
Thanks
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Hi Karthik,
Generally what projects do in ci.centos.org is to use Jenkins as the orchestrator, and do all the heavy lifting on the 'provisioned' machine, including cloning the test harness itself.
So in your example you could do something like:
vagrant ssh -c "git clone <url_of_your_test_suite>; ./runtests.sh"
That would pull down a copy of the t_functional suite into your fresh vagrant box.
Cheers!
-- Brian
Thanks Brian for your response. I actually read the console outputs of the builds https://ci.centos.org/view/CentOS-Core-QA/job/CentOS-Core-QA-t_functional-c6-64/390/consoleFull and got some better idea on how its done. I looked for the script */home/centos-core/centos_ci_run.py *and found it here https://github.com/athmane/centos-qa-ci-run/blob/master/centos_ci_run.py and OH! it talks to admin.ci.centos gets the right VM scp's the test suite and runs..... Sorry I couldn't get how the .*/runtest.sh* is triggered as its not here https://github.com/athmane/centos-qa-ci-run/blob/master/centos_ci_run.py#L54 as expected and its not anywhere in the repo ? Can you help please ?
Thanks
On Wed, Feb 24, 2016 at 12:42 AM, Brian Stinson brian@bstinson.com wrote:
On Feb 23 23:24, karthik kumar wrote:
Hi all, My name is Karthik. In our company we are planning have our own t_functional testing running and add more tests and contribute back to
the
community. To start with planning to run test suite in Vagrant VM and got struck in pushing the test suite to Vagrant VM and run the ./runtest.sh I know I can have a "Execute Shell" block in Jenkins with vagrant ssh
-c
"git clone xxxx" and vagrant ssh -c "./runtests.sh" but it doesn't look
the
right way to do with Jenkins !! Isn't it ? My blind guess on whats being done in ci.centos is kickstarting machine/provisioning VM, making it as jenkins-slave and running the job on it ?
So can you please advice how test suite is pushed to target
Machine/VM ?
Thanks
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Hi Karthik,
Generally what projects do in ci.centos.org is to use Jenkins as the orchestrator, and do all the heavy lifting on the 'provisioned' machine, including cloning the test harness itself.
So in your example you could do something like:
vagrant ssh -c "git clone <url_of_your_test_suite>; ./runtests.sh"
That would pull down a copy of the t_functional suite into your fresh vagrant box.
Cheers!
-- Brian
-
Brian Stinson -
karthik kumar