| Key: |
QB-1641
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Steve Luo
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 25/May/13 10:50 AM
Updated: 31/May/13 08:07 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
5.0.21
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
From time to time QB refuses to generate changeset with message:
09:10:41,265 WARN - Ignoring fetching changes because the start revision (e68cd7bd6d5efb9197d13f403ab07c48e35fc74b) seems elder than end revision (e2b0ce505a98afc12efc2367adc30b6d9e826697).
In many of our projects people develop on multiple development platforms, sometimes they have wrong local clock settings.
Then even though "start revision" preceeds "end revision" in the history tree, QB does not generate changest due to timestamps.
Could you turn off this additional check, or at least provide us means to do so?
|
|
Description
|
From time to time QB refuses to generate changeset with message:
09:10:41,265 WARN - Ignoring fetching changes because the start revision (e68cd7bd6d5efb9197d13f403ab07c48e35fc74b) seems elder than end revision (e2b0ce505a98afc12efc2367adc30b6d9e826697).
In many of our projects people develop on multiple development platforms, sometimes they have wrong local clock settings.
Then even though "start revision" preceeds "end revision" in the history tree, QB does not generate changest due to timestamps.
Could you turn off this additional check, or at least provide us means to do so? |
Show » |
|
Turn off timestamp check when fetching changes from git or hg
For
QB-1139, you can change the timestamp to use the author date or committer date and this timestamp will be displayed in the changes report tab, but will still check the timestamp for changes. While this issue will totally remove the detecting timestamp and instead will use below command to detect the changes:git log start..end
So, although the start revision is elder than end revision when your local time is not accurate, the changes still can be detected which is same as the command's output.