• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: git-plugin
• Labels:

  • hook
  • jenkins
  • parameter
  • stash
• Environment:

  Windows server 2008,
  Jenkins 1.590
  git-plugin 2.3.1

[JENKINS-25846] Parameterized job for branches with git hook doesn't work.

Antoine Morisseau created issue - 2014-12-01 14:45

Antoine Morisseau made changes - 2014-12-01 14:47

Description

Original: 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 ) Kind regards,

New: 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 ) Kind regards,

Antoine Morisseau made changes - 2014-12-01 14:51

Description

Original: 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 ) Kind regards,

New: 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 ) Kind regards,

Antoine Morisseau made changes - 2014-12-01 17:56

Description	Original: 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 ) Kind regards,	New: 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,
Environment	Original: Windows server 2008, Jenkins 1.590 git-plugin 2.3	New: Windows server 2008, Jenkins 1.590 git-plugin 2.3.1

Antoine Morisseau made changes - 2014-12-02 15:05

Description

Original: 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,

New: 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,

Antoine Morisseau made changes - 2014-12-02 15:06

Description

Original: 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,

New: 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,

Antoine Morisseau made changes - 2014-12-02 15:07

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Antoine Morisseau made changes - 2014-12-02 15:13

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-26 00:01

Workflow

Original: JNJira [ 159827 ]

New: JNJira + In-Review [ 208264 ]