[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Horst Krause commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I submitted pull request #304. https://github.com/jenkinsci/git-plugin/pull/304 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Horst Krause commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I linked some issue also struggeling with GIT-Sonar integration. Seems to be a quite common problem and would be very nice to get a solution. Especially as it seems to be quite simple for you. I would have provided the pull request, but the tests don't pass even before doing any change. Do I need any special setup on windows? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Mark Waite commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I don't intend to change the 2.0 behavior of the GIT_BRANCH variable as returned by the plugin. It includes the remote and the branch name as described by the entry on the wiki page. Unit tests were added a year ago to assure that behavior would be retained across versions of the plugin. If someone wants to submit a pull request for an additional variable which contains the branch name without the remote, I'm willing to evaluate that. The pull request should include unit tests which confirm the behavior of the new variable. If such a pull request is submitted, it must not change the behavior of the existing GIT_BRANCH variable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Horst Krause commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH The same for me. Updating to Sonar 5 just because of the slashes is quite an overkill. For example the Build Name Setter Plugin already gets GIT_BRANCH as input and just displays the shortened branch name. I would like the same for the sonar plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey reopened JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH I would like to see this issue reopened and the original change reverted. It is not possible to use the current variable with the sonar plugin: sonar.branch=$GIT_BRANCH breaks as the branch must be a branch, not an append of GIT_REMOTE and GIT_BRANCH. The documentation even says that this variable, called GIT_BRANCH, contains the remote and the branch separated by a slash. If you need the remote add a new variable called GIT_REMOTE please. There are many situations where string manipulation is not available and so expecting me to split on slash is not reasonable and not possible. Change By: Tim Pizey (06/Jan/15 11:10 AM) Resolution: WontFix Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey updated JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH Change By: Tim Pizey (06/Jan/15 11:30 AM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey started work on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH Change By: Tim Pizey (06/Jan/15 11:30 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Kevin Burge commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH While I was able to work around this issue (using CMake and Regular Expressions), as an end user, I can see Tim Pizey's point and agree. Another possibility is to add a variable in addition to GIT_REMOTE that has today's GIT_BRANCH value, like GIT_REF, or GIT_UPSTREAM_BRANCH or something like that. So, if anyone is depending on the current logic, they can simply rename the the variable they are referencing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Tim Pizey commented on JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH SonarQube 5.0 does/will support slashes in branch names: https://jira.codehaus.org/browse/SONAR-3718 I still do not want all my branches to be prefixed with 'origin/'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
