Hello,

We have an issue quite annoying in Jenkins and the git-plugin in our case.

We have some projects that have severals branches that we are working on it.
We would like to be able to manually start a build on a selected branche (So we have to create a parameterized build and thanks to Stash and a plugin https://wiki.jenkins-ci.org/display/JENKINS/StashBranchParameter we can retrieve the list of existing branche easily )

So in order to do that we use a env variable ${BRANCHES} in order to pass in into the Branches to build section. (i specify */${BRANCHES})

So manually it work wonders !

But now we want to be able to trigger a build from the same Job from a git push thanks to the hook available.
We are using Stash and the Stash notifier plugin to the web hooks.
But it doesn't work if we specified */${BRANCHES} in the Branches to build section.
If we specify */* the trigger work. But the manual mode doesn't work anymore.

even by putting the ${BRANCHES} default value at * it still doesn't work.

The only workaround avaible for now is to create two job. One for the manual and one for the git hook...

I think my issue is related to this issue since i use the Stash plugin to trigger the notification : ( https://issues.jenkins-ci.org/browse/JENKINS-25708 )

-I saw the resolved issue ( https://issues.jenkins-ci.org/browse/JENKINS-14276 )
so i did the update in hope to fix my issue.-

The variable is now resolved but the issue come from a non reset variable.
it's like the workspace of the job is not properly reset.

Kind regards,