Dennis Schumann

Perhaps the plugin can check for those variables but it's not aware of jenkins and it's configuration.

I can't tell you as we only use it with git

Hey there are 2 tasks that do they version increment. 1. unSnapshotVersion which makes 2.1.0-SNAPSHOT to 2.1.0 for example and 2. updateVersion that increases the version and adds a -SNAPSHOT...

Works for me ``` task printDeps { doLast { project.rootProject.buildscript.configurations.each { config -> config.dependencies.each { dep -> logger.warn("Dep: " + dep.name) } } } } ``` As buildScript dependencies are...

Yes that's right. Sorry for that

The problem is that the build directory is not in the .gitignore file. But I think on your local machine you have it in there and maybe have your .gitignore...

But the plugin is doing a "git status" and therefor it should ignore it the same way as git does. Do you have a repository that I can test against?...

First thing that comes to my mind is that jenkins probably runs into an infinite loop as the plugin pushes the changes to remote which might trigger another build? It...

pushReleaseVersionBranch was added in 2.8.0 Sorry as I see I forgot to update the Changelog :/

@jjkavalam Should not be related to this as GitAdapter should only be used for git projects I think. Do you have this issue in git too?