Issue Summary

There are two major problems currently seen with test cases processing in Bamboo

1. During the build result processing, post the build completion, if the test case count is high processing might take a lot of time and can keep the thread occupied to process the results which in in turn might block other build results from being proceed.

2. During viewing the buildresults post build completion, if the test count is abnormally high for a particular build result, it might take a long time to display that result

Both of the above problems originate because of long running SQL queries for the test cases.

Solution

There should be a solution designed at both Global and plan level to tackle this.

1) At the Global level, a JVM parameter if set would prevent any test cases to be written to DB and automatically the test cases could be added as an artifact

2) At a plan level, a parameter can be added, which if enabled would stop Bamboo to process the test cases into the database and would automatically add it as a artifact

The idea is to prevent long running SQL queries which blocks the threads.