|
||||||||
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't detect labeled changes on a branch
cedric.jo...@kisters.de (JIRA) Wed, 12 Sep 2012 01:03:44 -0700
- [JIRA] (JENKINS-15012) CVS Plugin doesn'... cedric.jo...@kisters.de (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... cedric.jo...@kisters.de (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... cedric.jo...@kisters.de (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... cedric.jo...@kisters.de (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15012) CVS Plugin d... michael.m.cla...@gmail.com (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.