Bamboo Export Fails due to Missing Build Trigger Reason
Symptoms
Bamboo export fails with exception below:
2010-06-10 01:01:10,749 INFO [QuartzScheduler_Worker-6] [BambooMapper] ... PLAN-KEY-1905
2010-06-10 01:01:10,763 ERROR [QuartzScheduler_Worker-6] [ScheduledBackupJob] java.lang.NullPointerException
at com.atlassian.bamboo.migration.ProjectMapper.exportBuildResultSummaries(ProjectMapper.java:301)
at com.atlassian.bamboo.migration.ProjectMapper.exportBuilds(ProjectMapper.java:256)
at com.atlassian.bamboo.migration.ProjectMapper.exportXml(ProjectMapper.java:202)
at com.atlassian.bamboo.migration.XmlMigrator.exportXml(XmlMigrator.java:224)
.....
at com.atlassian.bamboo.migration.XmlMigrator$$EnhancerByCGLIB$$d765d363.exportXml(<generated>)
at com.atlassian.bamboo.migration.ImportExportManagerImpl$1.call(ImportExportManagerImpl.java:55)
at com.atlassian.bamboo.migration.ImportExportManagerImpl$1.call(ImportExportManagerImpl.java:44)
at com.atlassian.bamboo.buildqueue.manager.LocalAgentManagerImpl.executeIfIdle(LocalAgentManagerImpl.java:790)
.....
at $Proxy22.executeIfIdle(Unknown Source)
at com.atlassian.bamboo.migration.ImportExportManagerImpl.bambooExport(ImportExportManagerImpl.java:43)
.....
Cause
The build trigger reason is missing, thus Bamboo is attempting to write a null value to XML file.
Resolution
Delete the faulty build result.
You can delete the faulty build result. To find out which build result to delete, review the Bamboo logs to find out which build result was being exported when the issue occurred.
Update the null value column in the database.
Alternatively, if you don't want to lose the build result. Then, you can set the null value column using SQL:
update BUILDRESULTSUMMARY set TRIGGER_REASON = 'com.atlassian.bamboo.plugin.system.triggerReason:ManualBuildTriggerReason' where TRIGGER_REASON = '' OR TRIGGER_REASON is null;
Last modified on Nov 21, 2012
Powered by Confluence and Scroll Viewport.