|
||||||||
|
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/groups/opt_out.
That message "Result has multiple lines" is not clear enough about what is really happening. Sorry about that.
I suspect the root cause of the problem is that the command "git rev-parse master^{commit}" (or some variant) is reporting more than one line of output. That is unexpected, since master^{commit} should report that the working repository used by Jenkins for that specific job has an ambiguously revision named "master". There are two or more things which can legitimately resolve the name "master^{commit}" for the "git rev-parse" command.
If you're interested in seeing the test case in the git-client-plugin which shows the problem, look at test_jenkins_11177 in https://github.com/jenkinsci/git-client-plugin/blob/master/src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java#L766 . The bug report which inspired that test was
JENKINS-11177.I'm not sure what's causing the case you've detected, since that bug was fixed over 6 months ago. Could you run the "git rev-parse master^{commit}" command in that repository and attach its output? There must be more cases where that is not handled correctly.
Looking at the source code, and making guesses based on the stack trace, I think the problem comes from the revParse which is used to read the names of the branches.