| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is possible for a git branch to have a / in it.
Source copy from host to VM used relative path on
the assumption that VM vagrant dir will always be
three levels down the topdir of repo. This assumption
breaks when git branch has a / in it.
Of the two solutions to fix it:
a. Mangle the git branch name to not have a /
b. Accomodate the possibility of have a / in git branch name.
I have chosen b) because that looks cleaner.
Change-Id: I6b71c31da2f5f7c349d6d6882767768b2534d14f
BUG: 1291537
Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
Reviewed-on: http://review.gluster.org/13355
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were quite a few places where exiting the script
made more sense.
More debug messages have been added.
Move back to top directory after the script is complete.
Change-Id: I2a66ee3a68c41a3acd0b7168c56b801fb5567e5f
BUG: 1291537
Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
Reviewed-on: http://review.gluster.org/13175
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Michael Adam <obnox@samba.org>
|
|
|
This introduces a mechanism using which a developer
could easily test the Gluster code in a VM environment.
Also, it will help bring uniformity in the environments
used by various developers.
How to use:
1. git checkout -b custom-branch-name
2. Make changes
3. Execute ./run-tests-in-vagrant.sh
What happens in the background:
1. A new directory is created:
tests/vagrant/vagrant-custom-branch-name
It will serve as the Vagrant dir which has the
Vagrantfile and related ansible playbooks.
The VM is started using Vagrant and provisioned
using ansible.
2. The source dir is recursively copied over to the
VM under /home/vagrant/glusterfs.
3. Gluster is source installed in VM.
What happens in the foreground:
1. run-tests.sh is executed in VM using ssh and output is displayed
in the same terminal with option to use ctrl-c to interrupt the test
midway. The VM would still persist and you could ssh into it.
Also, you can checkout a different branch elsewhere and execute
run-tests-in-vagrant.sh there to get another VM which would
execute tests on that code.
If you wish to make some changes in the code, you could:
a. Change the code in host and run the script again to repeat
the whole process.
OR
b. vagrant ssh into the VM and make the changes in the VM.
Co-authored-by: Kaushal M <kaushal@redhat.com>
Co-authored-by: Michael Adam <obnox@samba.org>
Change-Id: Ic87801172c8b614cdecbdf2a765e1b3370a5faf7
BUG: 1291537
Signed-off-by: Michael Adam <obnox@samba.org>
Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
Reviewed-on: http://review.gluster.org/12753
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
|
