Add Vagrant VMs & combine it with gitlab-ci #320
Conversation
There was a problem hiding this comment.
This looks like amazing work to me although I can't honestly assess the accuracy of those scripts. I have VMs on the Mac for fedora, arch, ubuntu and centos. If you'd like me to run those scripts and provide feedback, please ask and I'll get that done on Wednesday or Thursday.
There was a problem hiding this comment.
Great work @D4N !
I have worked with Vagrant before and I know how time-consuming this kind of task could be. It's a super valuable contribution and I am sure it will let us reproduce issues/bugs reported by users in different distributions.
|
|
||
| case "$distro_id" in | ||
| 'fedora') | ||
| dnf -y --refresh install gcc-c++ clang cmake make ccache expat-devel zlib-devel libssh-devel libcurl-devel gtest-devel which dos2unix |
There was a problem hiding this comment.
[question] I noticed that you are installing gcc and clang in all the different distros. Are you using both in gitlab?
There was a problem hiding this comment.
Yes, I am. Gitlab builds every combination of gcc/clang, Release/Debug and shared/static library.
contrib/vms/README.md
Outdated
| Please install [Vagrant](https://www.vagrantup.com/) and a supported provider | ||
| (e.g. libvirt, VirtualBox). | ||
|
|
||
| Choose a box from the above list and run: |
There was a problem hiding this comment.
[suggestion] I think it would be good to indicate that the user has to run this command from the directory where the Vagrantfile is.
There was a problem hiding this comment.
That's a good idea. I always do that automatically, so I just forgot.
D4N
force-pushed
the
vagrant_vms
branch
2 times, most recently
from
a71fc39 to
4e46a64
Compare
|
@clanmills You don't have to run those scripts yourself. Vagrant is a tool that creates VMs for you, so in case you would like a fresh Fedora 28 vm, just do a @piponazo Thanks, it was not too much work to get it running, since the major undertaking has been already done for the gitlab CI. Unfortunately it is not ready yet, as the OpenSUSE vm does not really work (it fails to install cmake..., don't know what to do there though as it requires user intervention) and I have not yet tested Archlinux. |
|
@D4N good to know. I can give a look to the OpenSUSE issue with CMake. |
|
@piponazo You can give it a try. The issue is that there are some file package conflicts when installing cmake (and later with git too). I guess that it can be solved by upgrading the image before doing anything else (OpenSUSE Tumbleweed is a rolling release distro, so it can happen that they have to push breaking changes) via |
D4N
force-pushed
the
vagrant_vms
branch
2 times, most recently
from
dd312ff to
41cc2d2
Compare
- add Vagrantfile to contrib/vms - add custom provisioning via shell scripts - move gitlab-ci before_script: to ci/install_dependencies.sh which is also used by vagrant - change COPR setup on CentOS 7 (yum-plugin-copr does not seem to work)
|
I played around with OpenSUSE VM but couldn't get it to provision automatically, since Unless there are complains, I'd merge this once the CI is green. |
This PR adds the vagrant boxes mentioned in #315.
Summary of the changes:
contrib/vmsci/install_dependencies.shwhich is also used by vagrant