|
||||||||
|
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.
Can you try whether upgrading to 0.4.0 solves your problem or not?
Otherwise would it be possible give the URL where your experience this problem. I suspect that we have a weird git commit with a comment that causes havoc.
Or you could checkout the git-parameter plugin, add lines like
LOGGER.log(Level.INFO, "generateContents add SHA1 " + r.getSha1String());
LOGGER.log(Level.INFO, "generateContents add prettyRevisionInfo " + r.prettyRevisionInfo(newgit, r));
before the calls to paramList.put.
Then call mvn clean install to build the plugin. And test it by adding the target/git-parameter.hpi via http://jenkins-url/pluginManager/advanced. The output of the jenkins log should then more details.