Low Found on customer data:
When test case name exceeds 255 chars, the import fails. Several issues here:
1. Import status is cryptic and should be improved:
Time Level Type Description Exception
2010-04-08 12:45:56 fatal bootstrap Bamboo has encountered errors while upgrading. Please resolve these errors and restart Bamboo. Upgrade task for build 1825 failed with exception: null
2. Maybe the test case name should be extended (since we now know it's to short for hierarchical test case names). Note: varchar is limited to 255 chars on some dbs (for example MySQL has to be >=5.0.3). So, it's not as easy as it seems. We could also switch to text from varchar (but we also need to verify db support for that).
3. What to do when such test case is encountered during Bamboo build processsing? Options: truncate, skip.
4. How should it affect the whole import? Options: truncate, skip.
5. Import stopped much later than at the point exception was detected (existing processing threads continued).
I will fix 1 and 5.
I need opinions on 3 and 4. I vote truncate.
[BAM-5624] Depending on underlying database, test case import can fail when test case name is too long
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1436482 ] | New: JAC Bug Workflow v3 [ 3380015 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1417933 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1436482 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 610000 ] | New: Bamboo Workflow 2016 v1 [ 1417933 ] |
| Workflow | Original: Bamboo Workflow 2014 [ 604969 ] | New: Bamboo Workflow 2014 v2 [ 610000 ] |
| Workflow | Original: Bamboo Workflow 2010 [ 208890 ] | New: Bamboo Workflow 2014 [ 604969 ] |
| Fix Version/s | New: 2.6 [ 15056 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: To be reviewed [ 10026 ] | New: Resolved [ 5 ] |
| Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Description |
Original:
Found on customer data:
When test case name exceeds 255 chars, the import fails. Several issues here: 1. Import status is cryptic and should be improved: Time Level Type Description Exception 2010-04-08 12:45:56 fatal bootstrap Bamboo has encountered errors while upgrading. Please resolve these errors and restart Bamboo. Upgrade task for build 1825 failed with exception: null 2. Maybe the test case name should be extended (since we now know it's to short for hierarchical test case names). Note: varchar is limited to 255 chars on some dbs (for example MySQL has to be >=5.0.3). So, it's not as easy as it seems. We could also switch to text from varchar (but we also need to verify db support for that). 3. What to do when such test case is encountered during Bamboo build processsing? Options: truncate, skip. 4. How should it affect the whole import? Options: truncate, skip. 5. The whole import was processed and did not stop at the point exception was detected (new processing threads were started). I will fix 1 and 5. I need opinions on 3 and 4. I vote truncate. |
New:
Found on customer data:
When test case name exceeds 255 chars, the import fails. Several issues here: 1. Import status is cryptic and should be improved: Time Level Type Description Exception 2010-04-08 12:45:56 fatal bootstrap Bamboo has encountered errors while upgrading. Please resolve these errors and restart Bamboo. Upgrade task for build 1825 failed with exception: null 2. Maybe the test case name should be extended (since we now know it's to short for hierarchical test case names). Note: varchar is limited to 255 chars on some dbs (for example MySQL has to be >=5.0.3). So, it's not as easy as it seems. We could also switch to text from varchar (but we also need to verify db support for that). 3. What to do when such test case is encountered during Bamboo build processsing? Options: truncate, skip. 4. How should it affect the whole import? Options: truncate, skip. 5. Import stopped much later than at the point exception was detected (existing processing threads continued). I will fix 1 and 5. I need opinions on 3 and 4. I vote truncate. |