Closed Bug 1265507 Opened 10 years ago Closed 10 years ago

Make repository "last modified" date more accurate

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gps, Assigned: gps)

References

Details

The "last modified" date reported by the Mercurial web interface at e.g. https://hg.mozilla.org/ is based on the mtime of .hg/store/00changelog.i. When we stand up new servers, we perform a `hg clone` and the mtime of this file is the time we perform that clone. So, for the new hgweb[11-14] servers, "last modified" is being reported within the past few weeks. We should have a script that can set the mtime of .hg/store/00changelog.i from either a) the mtime on the master server b) the time of the last push so the "last modified" date is more accurate. There is a slight chance this could muck with repo freshness checking in Mercurial internals. But I'm pretty sure Mercurial compares equivalence of mtime values, not greater/less than comparisons (which are subject to clock skew and therefore not as reliable). So we should be good moving the mtime backwards.
And deployed and executed in prod. I also changed the "last modified" string to RFC 3339 so it is easier to read.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Depends on: 1263679
Blocks: 1263679
No longer depends on: 1263679
You need to log in before you can comment on or make changes to this bug.