Bamboo startup or backup fails when the skipped test count has a null value
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Bamboo fails to start or backup fails. The following appears in the log files:
1
2
Caused by: org.springframework.orm.hibernate3.HibernateSystemException: Null value was assigned to a property of primitive type setter of com.atlassian.bamboo.resultsummary.tests.TestResultsSummaryImpl.skippedTestCaseCount; nested exception is org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.atlassian.bamboo.resultsummary.tests.TestResultsSummaryImpl.skippedTestCaseCount
Diagnosis/Cause
The root cause of this issue is that the BUILDRESULTSUMMARY table has a column skipped_test_count which can only accept an integer value. Now if you have some builds with the result summary saved with a null value for that column, then bamboo complains and fails with the error above. You can check this by running the below command:
1
select * from BUILDRESULTSUMMARY where skipped_test_count is null;Resolution
Shutdown Bamboo,
Backup the Bamboo database
Run the query below and restart Bamboo
1
update BUILDRESULTSUMMARY set skipped_test_count=0 where skipped_test_count is null;Was this helpful?