|
||||||||
|
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)

Somehow, I agree. However, it would be nice to get this "functionality" back if there is any easy/clean possibility to do so. CVS build triggers could be replaced by time based triggers for branches, but even then, we still miss a complete ChangeLog.