When we tried to set up CVS integration, the service failed with an ugly NullPointerException:

java.lang.NullPointerException
at org.netbeans.lib.cvsclient.command.BasicCommand.getFileEndingWith(BasicCommand.java:150)
at org.netbeans.lib.cvsclient.command.log.LogBuilder.createFile(LogBuilder.java:295)
at org.netbeans.lib.cvsclient.command.log.LogBuilder.processWorkingFile(LogBuilder.java:221)
at org.netbeans.lib.cvsclient.command.log.LogBuilder.parseLine(LogBuilder.java:157)
at com.atlassian.jira.vcs.cvsimpl.CvsRepositoryUtilImpl$1.parseLine(CvsRepositoryUtilImpl.java:78)
at org.netbeans.lib.cvsclient.command.BuildableCommand.messageSent(BuildableCommand.java:94)
at org.netbeans.lib.cvsclient.event.MessageEvent.fireEvent(MessageEvent.java:96)
at org.netbeans.lib.cvsclient.event.EventManager.fireCVSEvent(EventManager.java:107)
at org.netbeans.lib.cvsclient.response.MessageResponse.process(MessageResponse.java:52)
at org.netbeans.lib.cvsclient.Client.handleResponse(Client.java:444)
at org.netbeans.lib.cvsclient.Client.processRequests(Client.java:405)
at org.netbeans.lib.cvsclient.command.log.LogCommand.execute(LogCommand.java:132)
at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java:488)
at com.atlassian.jira.vcs.cvsimpl.CvsRepositoryUtilImpl.updateCvs(CvsRepositoryUtilImpl.java:87)
at com.atlassian.jira.vcs.cvsimpl.CvsRepository.updateCvs(CvsRepository.java:95)
at com.atlassian.jira.vcs.DefaultRepositoryManager.updateRepository(DefaultRepositoryManager.java:446)
at com.atlassian.jira.vcs.DefaultRepositoryManager.updateRepositories(DefaultRepositoryManager.java:406)
at com.atlassian.jira.service.services.vcs.VcsService.run(VcsService.java:48)
at com.atlassian.jira.service.JiraServiceContainer.run(JiraServiceContainer.java:51)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:50)
at org.quartz.core.JobRunShell.run(JobRunShell.java:147)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:387)
VcsService service finished.

I was able to hunt it down to this bug in the Netbeans cvs client: http://javacvs.netbeans.org/issues/show_bug.cgi?id=40347

Our cvs server is running version 1.11.11, not 1.12.5, but it is responding in exactly the same way as what's described in the bug comments.

Anyway, this bug is fixed in the netbeans cvs, so it would be great if you could update the version you are using.