| << Back to previous view |
|
[QB-497] Deleting a configuration with promoted builds doesn't cascade down into other configuations
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Paris Holley | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
If I have a configuration that I have had builds which have been promoted to other configurations, as soon as I delete the initial configuration, it complains about cannot find entity exceptions because the promotion_source_id has been null nor the row removed to reflect the deletion of the promoted source...
|
| Comments |
| Comment by Robin Shen [ 06/Jan/10 12:57 AM ] |
|
Hi Paris,
Are you sure this issue occurs on version 2.0.12? We should have get this issue fixed in that version. To verify, I downloaded 2.0.12 and can not reproduce it with below steps: 1. create two configurations, root/qa and root/release 2. edit advanced settings of root/qa and set the destination configuration as root/release 3. run root/qa to generate build 1.0.0 4. promote build 1.0.0 of root/qa to build 1.0.0 of root/release 5. delete configuration root/qa 6. switch to build 1.0.0 of configuration root/release and everything looks fine except that the promotion from link has been removed since the source build has been deleted. |
| Comment by Paris Holley [ 06/Jan/10 02:50 PM ] |
| No, its in 2.0.11 but I didn't see that as an option.. :) |
| Comment by Robin Shen [ 06/Jan/10 11:25 PM ] |
| Oh, my bad. We've forgot to add 2.0.11 to JIRA. Will make this as fixed in 2.0.12 now. |