Last modified: 2014-03-04 13:32:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
First Last Prev Next    This bug is not in your last search results.
Bug 49777 - Wikidata related repo fragmentation
Wikidata related repo fragmentation
Status: VERIFIED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: wmf-deployment
  Show dependency tree / graph
 
Reported: 2013-06-18 21:24 UTC by Sam Reed (reedy)
Modified: 2014-03-04 13:32 UTC (History)
9 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Sam Reed (reedy) 2013-06-18 21:24:53 UTC 
I'm not quite sure when this is going to be a problem for production (hashar has already been through it with beta as they run master)

But what new extensions need branching? What versions do we need to use of them? What configuration updates are needed? Do we need to have version dependent requires?

In 1.22wmf7 we're still using the 1.22wmf6 branches. The same will be the case for wmf8 if no newer branches are created (as previously occurred)/the updates are documented/notified in both config and make-wmf-branch.

It might not be an issue till 1.22wmf9 or later...

Halp?
Comment 1 Greg Grossmeier 2013-06-18 21:54:14 UTC 
I think the WikiData folks are planning on skipping cycles, ie: only update on the odd wmfXXs.

Otherwise, we could automatically create branches for it from either 1) the same branch point as the previous one or 2) an updated point based on a commit from the WikiData team.
Comment 2 denny vrandecic 2013-06-19 13:19:53 UTC 
What Greg says. We plan to skip cycles, and they might even be irregular. Actually I guess we should find a better way to handle this, but for now assume that we are only deploying every other week.
Comment 3 Antoine "hashar" Musso (WMF) 2013-06-19 18:43:13 UTC 
ccing Jeroen.

I have mailed Jeroen to get a confirmation.  He adopted Composer to define dependencies after I played with it back in January. So one can see the dependencies on  https://packagist.org/packages/wikibase/wikibase :

Jeroen confirmed by email the new dependency would be WikibaseDataModel (it is not in make-wmf-branch/default.conf ).  It has 'master' and '0.4.x' branches and a 0.4 tag.
Comment 4 Jeroen De Dauw 2013-06-26 12:25:40 UTC 
Indeed, the only relevant new repo is WikibaseDataModel. When running a version of Wikibase from before WikibaseDataModel was split off, then just use Wikibase. When running a version of it after the split was made, then WikibaseDataModel needs to be loaded as well.
Comment 5 Antoine "hashar" Musso (WMF) 2013-07-01 20:43:20 UTC 
The bug in beta was https://bugzilla.wikimedia.org/show_bug.cgi?id=49594 "" Class 'Wikibase\EntityId' not found on beta cluster""

Been fixed inside Wikibase somehow :)
Comment 6 Andre Klapper 2013-10-31 12:17:08 UTC 
[replacing wikidata keyword by adding CC - see bug 56417]
Comment 7 Lydia Pintscher 2014-03-03 15:26:29 UTC 
We're deploying from one repository now. I consider this fixed.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links