Last modified: 2012-08-23 09:10:50 UTC
All the pushing methods (single file, sync, etc) should do a !log wmf-config rev: 2000 mediawiki rev: 90000 after it has done the main !log This is useful debugging information for ops/shell personnel when they are trying to work out what information Regex grabbing it out of svn info in the 2 directories should be enough to give useful information
How would the mediawiki revision work in a het deploy environment? :D
Also, logging the wmf-config revid won't help as long as no one but me bothers to commit their changes to that repo (use /h/w/bin/configchange , it's a sync-file wrapper that does this for you) and the autocommit-after-30-minutes script is broken because wmf-config moved.
(In reply to comment #2) > Also, logging the wmf-config revid won't help as long as no one but me bothers > to commit their changes to that repo (use /h/w/bin/configchange , it's a > sync-file wrapper that does this for you) and the autocommit-after-30-minutes > script is broken because wmf-config moved. I commit to it, and I know JeLUFs script (which Hashar uses) does the svn commit, closes the bug and reports the revisions
(In reply to comment #3) > I commit to it, and I know JeLUFs script (which Hashar uses) does the svn > commit, closes the bug and reports the revisions Which script is this?
(In reply to comment #4) > (In reply to comment #3) > > I commit to it, and I know JeLUFs script (which Hashar uses) does the svn > > commit, closes the bug and reports the revisions > Which script is this? Ask Jens/Hashar, I think Jens wrote it
Looks obsoleted by git+gerrit?
