Last modified: 2014-08-22 01:02:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T38271, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36271 - [scap] Recompute and sync git version cache when sync-* are used
[scap] Recompute and sync git version cache when sync-* are used
Status: NEW
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
wmf-deployment
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://te.wikipedia.org/wiki/Special:...
:
: 43673 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-26 13:35 UTC by Niklas Laxström
Modified: 2014-08-22 01:02 UTC (History)
17 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Niklas Laxström 2012-04-26 13:35:54 UTC
See the linked URL. I've updated Narayam:
Previous HEAD position was e2d49f2... Merge "Remove rules that did nothing, correct errors, add new rules for simplification, use single rule instead of multiple where possible"
HEAD is now at 30c7b8c... Localisation updates from http://translatewiki.net.

Yet Special:Version still points to e2d49... (which is also useless, since it doesn't tell which branch it is in)
Comment 1 Nemo 2012-10-03 06:49:06 UTC
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.
Comment 2 Andre Klapper 2012-10-24 00:43:29 UTC
Nikerabbit: Narayam on http://te.wikipedia.org/wiki/Special:Version now states (7a72390). Is that correct?
Comment 3 Sam Reed (reedy) 2012-10-24 00:45:13 UTC
This only ever works if the git objects have been sync'd out...
Comment 4 Krinkle 2012-10-24 01:25:17 UTC
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.
Comment 5 Platonides 2012-10-28 18:48:27 UTC
I guess the scap script is explictely ignoring .git folder...
Comment 6 Krinkle 2012-10-29 21:40:43 UTC
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:
* http://wikitech.wikimedia.org/view/Wikimedia_binaries#sync-dir
* http://wikitech.wikimedia.org/view/Wikimedia_binaries#sync-file

etc.
Comment 7 Sam Reed (reedy) 2013-01-07 13:40:39 UTC
*** Bug 43673 has been marked as a duplicate of this bug. ***
Comment 8 Bryan Davis 2014-02-21 23:13:20 UTC
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).
Comment 9 Bryan Davis 2014-08-22 01:02:23 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links