[#QB-1641] Turn off timestamp check when fetching changes from git or hg

QuickBuild

Turn off timestamp check when fetching changes from git or hg

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

Description

« Hide

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?

All

Comments

Work Log

Change History

Sort Order:

Change by PMEase JIRA Administrator [26/May/13 02:48 PM]
Field	Original Value	New Value
Status	Open [ 1 ]	Resolved [ 5 ]
Assignee	Steve Luo [ steve ]
Resolution		Fixed [ 1 ]

Change by PMEase JIRA Administrator [26/May/13 02:48 PM]
Fix Version/s		5.0.21 [ 11455 ]

[ Permlink | « Hide ]

Alexey Shumkin [31/May/13 07:15 AM]

related to ~~QB-1139~~? or the same? ;)

[ Permlink | « Hide ]

Steve Luo [31/May/13 08:07 AM]

No, they are not the same.
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.