https://github.com/jonashackt/vagrant-github-actions

Example project showing how to run a Vagrant box on GitHub Actions
https://github.com/jonashackt/vagrant-github-actions

github-actions vagrant

Last synced: about 2 months ago
JSON representation

Example project showing how to run a Vagrant box on GitHub Actions

• Host: GitHub
• URL: https://github.com/jonashackt/vagrant-github-actions
• Owner: jonashackt
• License: mit
• Created: 2021-02-18T10:16:25.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2021-02-18T13:03:29.000Z (almost 4 years ago)
• Last Synced: 2024-10-10T05:37:26.459Z (2 months ago)
• Topics: github-actions, vagrant
• Homepage: https://stackoverflow.com/questions/66261101/using-vagrant-on-github-actions-ideally-incl-virtualbox
• Size: 8.79 KB
• Stars: 39
• Watchers: 3
• Forks: 9
• Open Issues: 4
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# vagrant-github-actions

[![Build Status](https://github.com/jonashackt/vagrant-github-actions/workflows/vagrant-up/badge.svg)](https://github.com/jonashackt/vagrant-github-actions/actions)

Example project showing how to run a Vagrant box on GitHub Actions

I have some history in this topic on how to run Vagrant on Cloud CI systems for OpenSource projects :) See https://stackoverflow.com/a/60615201/4964553 & https://stackoverflow.com/a/60380518/4964553 - since until somewhere in 2020 the only possible way was TravisCI with libvrt: https://github.com/jonashackt/vagrant-travisci-libvrt

What didn't work was plain VirtualBox on Travis: https://github.com/jonashackt/vagrant-travisci and also other CI platforms also did't work like AppVeyor https://github.com/jonashackt/vagrant-ansible-on-appveyor ([I didn't even try the others because of this](https://stackoverflow.com/questions/31828555/using-vagrant-on-cloud-ci-services)).

__BUT__ then the end of 2020 came and Travis defacto ended broad support for OpenSource (see https://github.com/codecentric/cxf-spring-boot-starter/issues/93) and I started to migrate all my repositories to [GitHub Actions](https://github.com/features/actions). I even blogged about it (tba when released).

And I finally found out, that [there's Vagrant activated (incl. nested virtualization) on GitHub Action MacOS environment](https://github.com/actions/virtual-environments/issues/433) ([not Linux](https://github.com/actions/virtual-environments/issues/183) or Windows currently).

### How to run Vagrant on GitHub Actions

So let's first add a [Vagrantfile](Vagrantfile) like this:

```

Vagrant.configure("2") do |config|

    config.vm.box = "generic/ubuntu1804"

    config.vm.define 'ubuntu'

    # Prevent SharedFoldersEnableSymlinksCreate errors

    config.vm.synced_folder ".", "/vagrant", disabled: true

end

```

Now add a MacOS environment powered GitHub Actions `vagrant-up.yml`:

```yaml

name: vagrant-up

on: [push]

jobs:

  vagrant-up:

    runs-on: macos-10.15

    steps:

      - uses: actions/checkout@v2

      - name: Cache Vagrant boxes

        uses: actions/cache@v2

        with:

          path: ~/.vagrant.d/boxes

          key: ${{ runner.os }}-vagrant-${{ hashFiles('Vagrantfile') }}

          restore-keys: |

            ${{ runner.os }}-vagrant-

      - name: Show Vagrant version

        run: vagrant --version

      - name: Run vagrant up

        run: vagrant up

      - name: ssh into box after boot

        run: vagrant ssh -c "echo 'hello world!'"

```

And since there's no stable release of VirtualBox for Big Sur (v11), well go with MacOS version 10.15 (which is currently also the `macos-latest` [environment on GitHub Actions](https://github.com/actions/virtual-environments))

We also use the https://github.com/actions/cache action here to cache our Vagrant boxes for further runs. Using `hashFiles('Vagrantfile')` will make sure we only create a new cache, if our `Vagrantfile` changed (and thus assume, that the box name is also different).