|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Hello Mark,
I tried to test the latest git plugin (2.0.4) with the latest git-client plugin (1.6.4) and due to another change in the git plugin the approach with "remotes/origin/..." does not work!
Commit ea5cad7e2759d0c9f5ed723fe590f982b0bb818d "
JENKINS-14026DefaultBuildChooser should handle smartly branches with /" causes the issue.When I specify "remotes/origin/feature1/master" the DefaultBuildChooser prepends the repo name (to String fqbn) "origin/remotes/origin/feature1/master" and for this String it is tried to get the head revision - which of course cannot work.
Shall I prepare another Pull Request or do you want to have a look into this?
Be aware that the help adjustments I contributed to the git plugin are already merged. The behaviour described there currently does not work due to above issue...
Thanks and regards,
Alex