The versions (of MW Core, skins, and extensions) listed on Special:Version is updated during a full scap. It is not updated by any of the sync-* commands.
This may lead to surprises when people are trying to verify what is deployed.
Version: wmf-deployment
Severity: enhancement
URL: http://te.wikipedia.org/wiki/Special:Version
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=53972
Add some recent Special:Version code contributors in case they have any idea on how to get it back to providing some useful version info.
Nikerabbit: Narayam on http://te.wikipedia.org/wiki/Special:Version now states (7a72390). Is that correct?
Generally ignore the commit has, look at the wmf version instead (1.21wmf1 etc.). Wikis are deployed in groups based on that. All wikis running on 1.21wmf1 will be running on the same git commit as there is only 1 code base of 1.21wmf1.
And generally whatever the latest head[1] of a branch is according to gerrit will be what is deployed.
[1] https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=heads
Converting ticket into a general task to somehow keep the .git info synchronised. So far that only happens with scap afaik.
No, scap is not explicitly ignoring anything. It synchronises the entire /common directory including all subfolders (including docroot, live-1.5/, php-1.21wmf1/ and anything inside it, such as .git/)
The problem is with the other sync scripts:
etc.
Syncing the entire .git directory is unnecessary. The php code (GitInfo.php) only needs .git/HEAD and the .git/refs/heads/* files to extract the SHA1.
Updated bug summary to clarify the scope of this issue (sync-* scripts).
Changing bug summary to reflect work that would need to be done to implement this. Since the resolution of bug 53972, scap creates json files containing git version information which are synced to the MediaWiki servers and read by Special:Version and other GitInfo consumers.
The sync-* family of scripts could be updated to recompute the git info cache and sync these files along with the specified payload. Due to construction of the python implementation of scap, this actually would not be incredibly difficult to implement.