[#BAM-916] Subversion Event Handler is not all that Null safe

Bamboo

Subversion Event Handler is not all that Null safe

Created: 26/Feb/07 03:04 AM Updated: 26/Feb/07 03:08 AM

Component/s:

None

Affects Version/s:

1.0

Fix Version/s:

1.0.1

Time Tracking:

Original Estimate:

30 minutes

Remaining Estimate:

30 minutes

Time Spent:

Not Specified

Participants:	Mark Chaimungkalanont [Atlassian]
Since last comment:	1 year, 39 weeks, 6 days ago
Number of comments:	0
Labels:

Description

« Hide

UpdateEventHandler throws a NullPointerException when SVN returns null action codes

com.atlassian.bamboo.repository.RepositoryException: Apache - Directory Server Trunk
	at com.atlassian.bamboo.repository.svn.SvnRepository.getChangesSinceLastBuild(SvnRepository.java:298)
	at com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126)
	at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166)
	at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114)
	at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77)
	at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
	at com.atlassian.bamboo.repository.svn.UpdateEventHandler.handleEvent(UpdateEventHandler.java:30)
	at org.tmatesoft.svn.core.wc.SVNBasicClient.dispatchEvent(SVNBasicClient.java:256)
	at org.tmatesoft.svn.core.wc.SVNBasicClient.dispatchEvent(SVNBasicClient.java:239)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.handleExternals(SVNUpdateClient.java:958)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:166)
	at com.atlassian.bamboo.repository.svn.SvnRepository.update(SvnRepository.java:618)
	at com.atlassian.bamboo.repository.svn.SvnRepository.getChangesSinceLastBuild(SvnRepository.java:275)
	... 6 more

All

Comments

Work Log

Change History

Sort Order:

There are no comments yet on this issue.