| << Back to previous view |
|
[QB-505] time of calculating SVN revision
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | AlSt | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | PMEase QuickBuild, 2.0.15 | ||
| Description |
|
Actually there are two problems:
1. Time of calculation QB2 checks for repository changes when a build is triggered (build condition). It later uses this revision for the checkout in the build. This works fine, if the build starts to run immediately. In our environment the build often has to wait in a queue and when it finally starts, the revision is outdated. -> check again for svn changes when the build starts or make this behavior configurable 2. Aggregate builds: If there are several builds in the queue and they get aggregated, the properties from the first one will be used. For the SVN revision this means that the "oldest" one gets executed, not the newest. -> With aggregation use the latest build. |
| Comments |
| Comment by Robin Shen [ 19/Jan/10 11:37 PM ] |
|
We will resolve the first issue in 2.1.x series. For the second issue, it should be already using the last build in the queue, and I verified this to be true for 2.0.15. Can you double check this?
Thanks |
| Comment by AlSt [ 20/Jan/10 10:01 PM ] |
|
I just checked the second issue in 2.0.15 and it is already using the latest build.
Tanks! |