Last modified: 2012-11-18 13:49:10 UTC
Right now on beta labs enwiki, Mediawiki, the AFTv5 extension, NewPageFeed extension, and Page Curation Toolbar all exist and function. Because we want to expose these extensions in the latest core code for testing and investigation, we want to have the latest viable versions always available on beta labs. Therefore we should have these sets of code deployed automatically to beta labs, particularly enwiki. Ideally this would be done through Jenkins, but in the meantime a shell script + crontab at reasonable intervals would suffice. Note: the current AFTv5 is deployed on prototype, but prototype will go EOL very soon, so moving AFTv5 to beta labs is a priority. The current NPF is deployed on ee-prototype, but hosting it in a more production-like environment is a key goal.
That is in my goal list for this week. I will first hack a shell script and a cronjob to handle that.
I think I had shared with you the wiki updating script.
I am rephrasing this bug to make it update ALL extensions automatically.
Change https://gerrit.wikimedia.org/r/#/c/22116/ Being tested on deployment-integration.
The script also need to update the l10n cache https://gerrit.wikimedia.org/r/#/c/22673/
(In reply to comment #5) > The script also need to update the l10n cache > https://gerrit.wikimedia.org/r/#/c/22673/ Change got merged which let the autoupdater update the l10n cache. The beta autoupdater https://gerrit.wikimedia.org/r/#/c/22116/ still pending review / merge.
Note Gerrit change #22116 is currently deployed on a labs instance so its review is not really blocking us. Thus lowering priority.
Looks like I forgot about this bug. The wmf beta autoupdater script has been running for quiet some time now. It is basic shell script being run on -bastion instance as mwdeploy user. An upstart script is provided to easily reload/restart it.
