⚓ T182326 Make one group1 wiki a client of testwikidata (preferably a test wiki)
Page Menu
Phabricator
Create Task
Maniphest
T182326
Make one group1 wiki a client of testwikidata (preferably a test wiki)
Closed, Resolved
Public
Actions
Edit Task
Edit Related Tasks...
Create Subtask
Edit Parent Tasks
Edit Subtasks
Merge Duplicates In
Close As Duplicate
Edit Related Objects...
Edit Commits
Edit Mocks
Mute Notifications
Protect as security issue
Assigned To
Ladsgroup
Authored By
Ladsgroup
Dec 7 2017, 2:23 PM
2017-12-07 14:23:21 (UTC+0)
Tags
Wikidata
(incoming)
Deployments
(To Triage)
Release-Engineering-Team (Watching / External)
User-Ladsgroup
(Done)
Referenced Files
None
Subscribers
Addshore
Aklapper
aude
daniel
demon
gerritbot
greg
View All 15 Subscribers
Description
So we could have a repo-client relationship with two different version numbers so we can avoid incompatibilities beforehand and avoid bugs like
T182243: Fatal in AffectedPagesFinder: Call to a member function getSiteLinkChanges() on a non-object (string)
Duplicate task from 2014:
T76470: have one testwiki (client) on the previous branch deployed (compared to the branch test.wikidata repo is on)
Details
Related Changes in Gerrit:
Subject
Repo
Branch
Lines +/-
Add test2wiki as a group1 wiki
operations/mediawiki-config
master
+1
-0
Move testwiki2 from group0 to group1
operations/mediawiki-config
master
+0
-1
Customize query in gerrit
Related Objects
Search...
Task Graph
Mentions
Duplicates
Status
Subtype
Assigned
Task
Invalid
None
T108946
[Epic] Improve the development infrastructure
Resolved
Ladsgroup
T182326
Make one group1 wiki a client of testwikidata (preferably a test wiki)
Mentioned In
T273435: test2wiki is in group1 rather than group0
T76470: have one testwiki (client) on the previous branch deployed (compared to the branch test.wikidata repo is on)
Mentioned Here
T76470: have one testwiki (client) on the previous branch deployed (compared to the branch test.wikidata repo is on)
T182243: Fatal in AffectedPagesFinder: Call to a member function getSiteLinkChanges() on a non-object (string)
Duplicates Merged Here
T76470: have one testwiki (client) on the previous branch deployed (compared to the branch test.wikidata repo is on)
Event Timeline
Ladsgroup
created this task.
Dec 7 2017, 2:23 PM
2017-12-07 14:23:21 (UTC+0)
Restricted Application
added a subscriber:
Aklapper
View Herald Transcript
Dec 7 2017, 2:23 PM
2017-12-07 14:23:21 (UTC+0)
thiemowmde
triaged this task as
High
priority.
Dec 7 2017, 2:34 PM
2017-12-07 14:34:43 (UTC+0)
thiemowmde
added subscribers:
aude
Addshore
thiemowmde
added a parent task:
T108946: [Epic] Improve the development infrastructure
Dec 7 2017, 3:25 PM
2017-12-07 15:25:17 (UTC+0)
thiemowmde
mentioned this in
T76470: have one testwiki (client) on the previous branch deployed (compared to the branch test.wikidata repo is on)
Dec 7 2017, 3:28 PM
2017-12-07 15:28:20 (UTC+0)
thiemowmde
updated the task description.
(Show Details)
Addshore
awarded a token.
Dec 7 2017, 3:29 PM
2017-12-07 15:29:10 (UTC+0)
Comment Actions
+1 we should do this. It is an easy way to spot possible issues with wikidata related compat deployments.
These cases will never be caught by beta because of the way beta updates vs production.
Ladsgroup
added a subscriber:
greg
Dec 7 2017, 3:36 PM
2017-12-07 15:36:23 (UTC+0)
Comment Actions
Making test2wiki a group1 wiki won't be super hard but
@greg
needs to sign it off first.
Addshore
added a comment.
Dec 7 2017, 3:37 PM
2017-12-07 15:37:36 (UTC+0)
Comment Actions
I think it would be less confusing to simply make a new wiki for this specific purpose.
greg
added a comment.
Dec 7 2017, 7:45 PM
2017-12-07 19:45:43 (UTC+0)
Comment Actions
Which makes sense? Give me the pros/cons (not looking for an RFC :P ).
daniel
added a comment.
Dec 7 2017, 8:06 PM
2017-12-07 20:06:03 (UTC+0)
Comment Actions
@Addshore
in which way would it be confusing? Who would be confused? What is test2wiki used for, specifically?
Adding a wiki is not as easy as it should be, so I suppose Ladsgroup is trying to avoid that trouble. If it was easy, I would also opt for a new wiki with a more descriptive name... though I can't think of one off-hand.
@greg
Both make sense, but making a new wiki is more overhead. The only reason to do that is to avoid confusion, as Adam says. Not sure how bad that confusion would actually be though.
Addshore
added a comment.
Dec 7 2017, 8:09 PM
2017-12-07 20:09:32 (UTC+0)
Comment Actions
In
T182326#3821139
@daniel
wrote:
@Addshore
in which way would it be confusing? Who would be confused? What is test2wiki used for, specifically?
Test2 is primarily used to trial and debug global and cross-wiki features in conjunction with
and
Test2 has been in gorup0 for rather a long time, and if people expect that and we change it, well, confusion follows.
Adding a wiki is not as easy as it should be, so I suppose Ladsgroup is trying to avoid that trouble. If it was easy, I would also opt for a new wiki with a more descriptive name... though I can't think of one off-hand.
@greg
Both make sense, but making a new wiki is more overhead. The only reason to do that is to avoid confusion, as Adam says. Not sure how bad that confusion would actually be though.
If making a new wikis is too hard then lets use something we have, but I think a new site would be the 'best' option.
daniel
added a comment.
Dec 7 2017, 8:12 PM
2017-12-07 20:12:19 (UTC+0)
Comment Actions
Test2 is primarily used to trial and debug global and cross-wiki features in conjunction with
and
The point of this request is that this test should cover the situation of the two wikis not being on the same branch. If we created a new site, all the testing that happened on the old site would then need to happen on the new site as well.
Addshore
added a comment.
Dec 7 2017, 9:05 PM
2017-12-07 21:05:32 (UTC+0)
Comment Actions
In
T182326#3821149
@daniel
wrote:
Test2 is primarily used to trial and debug global and cross-wiki features in conjunction with
and
The point of this request is that this test should cover the situation of the two wikis not being on the same branch. If we created a new site, all the testing that happened on the old site would then need to happen on the new site as well.
If you require 2 wikis to be on the new code (group0) in order to perform tests before that code gets pushed out to group 1 the following day then testwiki and test2wiki should remain in group0, I'm not saying we need that, but it seems like a thing others probably need / want.
If we move one of those wikis to group1 we risk improving the catchability of wikibase issues, but who knows what other issues could slip passed because we changed the setup for other global things.
Anyway, I don't feel too strongly either way, but I feel its a valid point :)
greg
added a project:
Deployments
Dec 7 2017, 9:39 PM
2017-12-07 21:39:02 (UTC+0)
aude
added a comment.
Edited
Dec 8 2017, 12:57 AM
2017-12-08 00:57:04 (UTC+0)
Comment Actions
In
T182326#3821144
@Addshore
wrote:
In
T182326#3821139
@daniel
wrote:
@Addshore
in which way would it be confusing? Who would be confused? What is test2wiki used for, specifically?
Test2 is primarily used to trial and debug global and cross-wiki features in conjunction with
and
Test2 has been in gorup0 for rather a long time, and if people expect that and we change it, well, confusion follows.
Adding a wiki is not as easy as it should be, so I suppose Ladsgroup is trying to avoid that trouble. If it was easy, I would also opt for a new wiki with a more descriptive name... though I can't think of one off-hand.
@greg
Both make sense, but making a new wiki is more overhead. The only reason to do that is to avoid confusion, as Adam says. Not sure how bad that confusion would actually be though.
If making a new wikis is too hard then lets use something we have, but I think a new site would be the 'best' option.
I don't think creating a new wiki is too difficult.
Not sure how much use such new wiki would get though for catching bugs, unless we setup some automated browser tests or something
demon
subscribed.
Dec 11 2017, 6:00 PM
2017-12-11 18:00:36 (UTC+0)
Comment Actions
We could move test2 to group1 and use that. Easiest solution, plus would get some extra traffic.
daniel
added a comment.
Dec 11 2017, 7:28 PM
2017-12-11 19:28:31 (UTC+0)
Comment Actions
@demon
I'm all for it!
greg
added a comment.
Dec 11 2017, 10:04 PM
2017-12-11 22:04:46 (UTC+0)
Comment Actions
Thanks
@demon
@Ladsgroup
take the reins?
Ladsgroup
added a comment.
Dec 12 2017, 10:53 AM
2017-12-12 10:53:55 (UTC+0)
Comment Actions
Sure
greg
edited projects, added
Release-Engineering-Team (Watching / External)
; removed
Release-Engineering-Team
Dec 12 2017, 10:40 PM
2017-12-12 22:40:13 (UTC+0)
gerritbot
subscribed.
Dec 17 2017, 3:53 PM
2017-12-17 15:53:01 (UTC+0)
Comment Actions
Change 398704 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[operations/mediawiki-config@master] Move testwiki2 from group0 to group1
gerritbot
added a project:
Patch-For-Review
Dec 17 2017, 3:53 PM
2017-12-17 15:53:01 (UTC+0)
gerritbot
added a comment.
Jan 4 2018, 1:47 AM
2018-01-04 01:47:02 (UTC+0)
Comment Actions
Change 398704
merged
by jenkins-bot:
[operations/mediawiki-config@master] Move testwiki2 from group0 to group1
Stashbot
subscribed.
Jan 4 2018, 1:50 AM
2018-01-04 01:50:05 (UTC+0)
Comment Actions
Mentioned in SAL (#wikimedia-operations)
[2018-01-04T01:50:05Z]
T182326
) (duration: 01m 02s)
Addshore
closed this task as
Resolved
Jan 4 2018, 10:13 AM
2018-01-04 10:13:16 (UTC+0)
Addshore
claimed this task.
Restricted Application
added a project:
User-Addshore
View Herald Transcript
Jan 4 2018, 10:13 AM
2018-01-04 10:13:16 (UTC+0)
Addshore
reassigned this task from
Addshore
to
Ladsgroup
Jan 4 2018, 10:13 AM
2018-01-04 10:13:26 (UTC+0)
Restricted Application
added a project:
User-Ladsgroup
View Herald Transcript
Jan 4 2018, 10:13 AM
2018-01-04 10:13:26 (UTC+0)
Addshore
removed a project:
User-Addshore
Jan 4 2018, 10:13 AM
2018-01-04 10:13:35 (UTC+0)
gerritbot
added a comment.
Jan 5 2018, 10:36 PM
2018-01-05 22:36:22 (UTC+0)
Comment Actions
Change 402445 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[operations/mediawiki-config@master] Add test2wiki as a group1 wiki
Tgr
subscribed.
Jan 6 2018, 1:21 AM
2018-01-06 01:21:57 (UTC+0)
Comment Actions
At a glance the special uses of test2wiki are:
test frontend for remote file repo logic, with testwiki as the backend
EventLogging testbed which uses its own Schema namespace instead of meta
Neither of those seem terribly important. I seem to recall test2 serving as a login wiki for test, but that doesn't seem to be the case now.
Please don't forget to document the new state on the test2 main page.
gerritbot
added a comment.
Jan 8 2018, 3:00 PM
2018-01-08 15:00:30 (UTC+0)
Comment Actions
Change 402445
merged
by jenkins-bot:
[operations/mediawiki-config@master] Add test2wiki as a group1 wiki
Stashbot
added a comment.
Jan 8 2018, 3:03 PM
2018-01-08 15:03:28 (UTC+0)
Comment Actions
Mentioned in SAL (#wikimedia-operations)
[2018-01-08T15:03:28Z]
T182326
(duration: 00m 50s)
thcipriani
mentioned this in
T273435: test2wiki is in group1 rather than group0
Feb 1 2021, 2:49 PM
2021-02-01 14:49:37 (UTC+0)
Maintenance_bot
removed a project:
Patch-For-Review
Feb 1 2021, 3:11 PM
2021-02-01 15:11:14 (UTC+0)
Maintenance_bot
moved this task from
Incoming
to
Done
on the
User-Ladsgroup
board.
Feb 1 2021, 3:15 PM
2021-02-01 15:15:14 (UTC+0)
bd808
merged a task:
T76470: have one testwiki (client) on the previous branch deployed (compared to the branch test.wikidata repo is on)
Nov 7 2024, 12:45 AM
2024-11-07 00:45:20 (UTC+0)
bd808
added subscribers:
JanZerebecki
thiemowmde
Tobi_WMDE_SW
Log In to Comment
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct.
Wikimedia Foundation
Code of Conduct
Disclaimer
CC-BY-SA
GPL
Credits
US