|
||||||||
|
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-15012) CVS Plugin doesn'... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... [email protected] (JIRA)

It seems the problem is the switch to 'rlog' for polling: since we move the branch tag to merge down changes from HEAD to branch, it will never see any new revision. However, this worked with 'update' before.
I don't know about the reasons to switch to 'rlog', but would it be possible to add a configuration parameter to choose how the polling is done? That would probably fix our issue.