bmuschko/gradle-vagrant-plugin

= Gradle Vagrant plugin image:https://github.com/bmuschko/gradle-vagrant-plugin/workflows/Build%20and%20Release%20%5BLinux%5D/badge.svg["Build Status", link="https://github.com/bmuschko/gradle-vagrant-plugin/actions?query=workflow%3A%22Build+and+Release+%5BLinux%5D%22"]

image:https://hyzxph.media.zestyio.com/blog-vagrant.svg[Vagrant Logo, scaledwidth="5%"]

Gradle plugin for managing link:http://www.vagrantup.com/[Vagrant] boxes.

== Usage

To use the plugin, include in your build script:

[source,groovy]

buildscript { repositories { mavenCentral() }

dependencies {
    classpath 'com.bmuschko:gradle-vagrant-plugin:3.0.0'
}

}

== Base plugin

If you want to create your own task for managing Vagrant, you should go with the base plugin. This option is usually helpful if you are dealing with multiple VMs in parallel. The base plugin provides all custom task types and preconfigures them with sensible defaults. To use the base plugin, add the following apply notation to your build script.

[source,groovy]

apply plugin: 'com.bmuschko.vagrant-base'

=== Custom task types

The base plugin provides the following custom task types:

=== Extension properties

The base plugin defines the following extension properties in the vagrant closure:

The recommended way for providing values to the Vagrantfile from the outside is to use environment variables. This is made possible through the nested configuration element environmentVariables. This element exposes the method variable that takes two parameters: the key and value for a environment variable. For each invocation of this method a new key/value pair is added to internal property named variables.

By default the plugin validates the installation of the Vagrant runtime and the selected provider. This validation logic can be disabled from your buildscript. This is made possible through the nested configuration element installation. This element exposes the method validate that take a single parameter.

=== Example

[source,groovy]

import com.bmuschko.gradle.vagrant.tasks.VagrantUp import com.bmuschko.gradle.vagrant.tasks.VagrantDestroy

ext { virtualBoxDir = file('virtualbox-box') fusionBoxDir = file('fusion-box') fusionProvider = 'vmware_fusion' }

task startVirtualBoxVm(type: VagrantUp) { description = 'Starts VM machine running on VirtualBox.' group = 'VirtualBox VM' boxDir = virtualBoxDir }

task stopVirtualBoxVm(type: VagrantDestroy) { description = 'Stops VM machine running on VirtualBox.' group = 'VirtualBox VM' boxDir = virtualBoxDir }

task startFusionVm(type: VagrantUp) { description = 'Starts VM machine running on VMware Fusion.' group = 'Fusion VM' boxDir = fusionBoxDir provider = fusionProvider }

task stopFusionVm(type: VagrantDestroy) { description = 'Stops VM machine running on VMware Fusion.' group = 'Fusion VM' boxDir = fusionBoxDir provider = fusionProvider }

== Convention plugin

If you want the plugin to preconfigure commonly-used tasks for you, you should go with the full-fledged convention plugin. This plugin is a viable option if you only have to deal with a single VM. To use the convention plugin, add the following apply notation to your build script.

[source,groovy]

apply plugin: 'com.bmuschko.vagrant'

=== Default tasks

The plugin defines the following tasks:

=== Example

[source,groovy]

vagrant { boxDir = file('~/dev/my-vagrant-box')

environmentVariables {
    variable 'IP', '192.168.1.33'
    variable 'OPERATINGSYSTEM', 'redhat'
}

installation {
    validate = false
}

}

import com.bmuschko.gradle.vagrant.tasks.Vagrant import com.bmuschko.gradle.vagrant.tasks.VagrantSsh

task vagrantListsBoxes(type: Vagrant) { description = 'Outputs a list of available Vagrant boxes.' commands = ['box', 'list'] }

task vagrantEcho(type: VagrantSsh) { description = 'Runs remote SSH command in Vagrant box.' sshCommand = "echo 'hello'"

dependsOn vagrantUp
finalizedBy vagrantDestroy