|
||||||||
|
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-15808) CVS plugin 2.7 br... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)
- [JIRA] (JENKINS-15808) CVS plugin 2... [email protected] (JIRA)

I tried to reproduce this on a clean Jenkins core v. 1.492
Installed Gerrit Trigger 2.6.0 And created a project; works
Upgraded CVS Plugin to 2.7 and reconfigured the job; works
Could it be something else in your combination that is causing it?