
Key: |
QB-277
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
Robin Shen
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 05/Sep/07 09:15 AM
Updated: 09/Sep/07 11:09 PM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
From customer:
I got the root cause of the problem, actually this is the problem only with the build those were rebuild again due to some reason and that's why there build ID got changed from previous. For a time being i have changed its value manually in database tables. But cant we have a procedure in which if a successful build triggered again its build version get updated in Jira table to which is static at the movement. I am not sure but i think it can be done by modifying the Quickbuild-Jira plug-in by adding a database "update" command just like "add" command in case of build is triggering again.
|
Description
|
From customer:
I got the root cause of the problem, actually this is the problem only with the build those were rebuild again due to some reason and that's why there build ID got changed from previous. For a time being i have changed its value manually in database tables. But cant we have a procedure in which if a successful build triggered again its build version get updated in Jira table to which is static at the movement. I am not sure but i think it can be done by modifying the Quickbuild-Jira plug-in by adding a database "update" command just like "add" command in case of build is triggering again. |
Show » |
No work has yet been logged on this issue.
|
|