|
||||||||
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 |
- [JIRA] (JENKINS-14365) Wacky number for cha... dwat...@mimsoftware.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-14365) Wacky number fo... dogf...@java.net (JIRA)
In fact reproducible without multiple-scms plugin, just on a plain job using Mercurial. The problem is in jenkins/core/src/main/resources/hudson/scm/SCM/project-changes.jelly which uses <li value="${c.revision}"> even though no getRevision method is defined in the core ChangeLogSet.Entry (MercurialChangeSet happens to define it without overriding).