v0.4.1 No functional changes, publishing configuration changes only

Now publishing directly to the Gradle Plugins Portal instead of first to my personal bintray gradle-plugins repository. This makes the plugin directly available after release, instead of having to wait for a sync to happen.

Note:
This release has NO functional changes!
This release purely happened to test the new way of publishing the plugin to the Gradle Plugins Portal.

v0.4.0 Finally windows support!

The plugin now also works on Windows, finally.
This is brought to you, by the contribution of @SchwingSK. Many thanks @SchwingSK!

v0.3.0: Add support for config files jobDsl command

Now supporting the config files jobDsl command
as described on Job-DSL-Commands.md#config-file

Thanks to @dlethin for contributing.

v0.2.0: Now supporting bindings in the `jenkinsJobDsl` section

You can now configure binding variables
in the jenkinsJobDsl section to mimic bindings on an
action Seed job in Jenkins.

With this, in your build.gradle file, you can configure the bindings:

jenkinsJobDsl {
    jobConfigs {
        from file('project.dsl.groovy')
    }
    binding = ['NAME': project.name]
}

and use them in your DSL script files, like:

job {
    name "${NAME}"
    description 'Single job example'
}

Where the NAME binding could be for example a
job parameter to your Seed job in Jenkins.

Thanks to @dlethin for contributing.

From now on, I will use Semantic Versioning