[#QB-1271] Git plugin incorrectly ignores fetching changes because author date order is not linear

QuickBuild

Git plugin incorrectly ignores fetching changes because author date order is not linear

Created: 18/May/12 12:25 AM Updated: 26/May/12 12:21 AM

Component/s:

None

Affects Version/s:

4.0.36

Fix Version/s:

4.0.40

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

When working with Gerrit, we frequently have multiple parallel commits outstanding which are not merged to master. When master has changed compared to the parent of these commits, we frequently rebase the commit on top of the current master. This means that while the CommitDates of the commits are linear in time, the AuthorDates are not linear (because AuthorDate reflects the time the commit was originally made, not when it was rebased to master).

QB git plugin fails to record history in this case:
00:05:32,610 [master>Clone@BUILDER:8811] WARN - Ignoring fetching changes because the start revision (11aea079bfe6e5688e5fe0f6f3a852aa286534f7) seems elder than end revision (06d5f002015f52af675d3028ce7794f8465541ed).

There is a similar issue http://track.pmease.com/browse/QB-1139 which was closed with resolution "Won't fix" - can you please comment?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Steve Luo [18/May/12 03:33 AM]

If you want to use AuthorDates instead of CommitDates, please change your 'Committer User Schema' field to:
'Author Name', or 'Author Email' or 'Author Name and Email'

that is the reason why I closed ~~QB-1139~~.

[ Permlink | « Hide ]

Magnus Hiie [18/May/12 03:57 PM]

Thanks for the quick response.

We are using "Author Name" as the "Committer User Schema". And we wouldn't like to switch to "Committer Name" because the committer does not necessarily have anything to do with the commit contents.

We would just like QB to not ignore commits (and report 0 SCM changes in build UI) when the AuthorDates are not linear in time.