Re: [Wikitech-l] Phabricator update
We are working on a page summarizing all what matters about the migration from Bugzilla to Phabricator: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla Your feedback and edits today help us offering better information to our thousands of Bugzilla users tomorrow. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
I am almost as excited as Isarra, except that pines prefer to compost creaky old things instead of setting them on fire. (: Will Bugzilla be available read-only during the transition? It would help to have those reports still available during downtime, along with instructions about how to queue bug reports while Bugzilla is unavailable and Phabricator is not yet online. Pine On Sep 22, 2014 5:15 PM, Isarra Yos zhoris...@gmail.com wrote: On 16/09/14 13:34, Quim Gil wrote: Hi, if you were wondering what is going on in Phabricator land... Summary: You can see https://phabricator.wikimedia.org , you can touch https://phab-01.wmflabs.org/ , you will have a chance to provide feedback about the Bugzilla migration before the migration, based on a test instance with a sample of bugs imported. In detail: * https://phabricator.wikimedia.org exists as a read-only instance and it contains the tasks that were migrated from the now decommissioned fab.wmflabs.org. Registration is disabled while we fix some tasks -- details at https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan . We will post here when the issues have been fixed. * We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is for testing and experimenting only. Anything in there can disappear in a whim. * When we open phabricator.wikimedia.org, the creation of new projects will be still disabled. Existing projects will be able to continue their work, but we are asking new projects to wait a few weeks, until we complete the Bugzilla migration. It's going to be still a bumpy road before Day 1, and we want to control the impact of these disruptions as much as possible. * RT migration will follow. Details will be shared in advance. * Bugzilla migration will follow. Details will be shared in advance as well, but we have a rough idea of the sequence of steps. Details available in the migration plan linked above, pasted here for convenience: 1. Earliest possible/expected date: October 06 but favoring Friday October 10 to interrupt engineering less (starting over the weekend). Bugzilla downtime expected of 1-3 days. Checklist: 2. Instructions to use Phabricator for bug reporting and project management. 3. Documentation of data and features that will not be available in Phabricator after the migration. Phabricator test instance available with a sample of Bugzilla reports imported automatically (say 1 of each 10, about 700 reports). 4. At least one week of margin to receive community feedback and implement improvements. 5. Documentation of the migration process detailing sequence of steps and timeline expected. 6. Go-NoGo meeting with the Phabricator team (Andre, Chase, Mukunda, Quim), Erik, Rob, MarkB, and Greg. Stay tuned. :) Thank you everyone for working on this. The transition cannot happen soon enough, as far as I'm concerned, so these updates are a shining beacon of hope. (I had to switch computers and now git review is completely broken for me, with apparently no fix available. Can we burn gerrit? In a huge fire? Please?) -I ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
It is exciting to see the excitement. :) On Tue, Sep 23, 2014 at 9:09 AM, Pine W wiki.p...@gmail.com wrote: Will Bugzilla be available read-only during the transition? Yes, and also after Day 1 for an indeterminate period of time, just in case. https://phabricator.wikimedia.org/T366 It would help to have those reports still available during downtime, along with instructions about how to queue bug reports while Bugzilla is unavailable and Phabricator is not yet online. Totally agreed. The exact scenario of the transition needs to be defined at https://phabricator.wikimedia.org/T473 These days I'm updating https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla with all the relevant information and links to ongoing tasks. Timely questions. Keep them coming, please, here or in the discussion page. On Sep 22, 2014 5:15 PM, Isarra Yos zhoris...@gmail.com wrote: (I had to switch computers and now git review is completely broken for me, with apparently no fix available. Can we burn gerrit? In a huge fire? Please?) According to https://www.mediawiki.org/wiki/Phabricator#Migration_timeline the deprecation of Gerrit is expected before 2015-03-31?, and at this point I can't stress the question mark enough. You still might need to fix your Gerrit problems... ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
On 16/09/14 13:34, Quim Gil wrote: Hi, if you were wondering what is going on in Phabricator land... Summary: You can see https://phabricator.wikimedia.org , you can touch https://phab-01.wmflabs.org/ , you will have a chance to provide feedback about the Bugzilla migration before the migration, based on a test instance with a sample of bugs imported. In detail: * https://phabricator.wikimedia.org exists as a read-only instance and it contains the tasks that were migrated from the now decommissioned fab.wmflabs.org. Registration is disabled while we fix some tasks -- details at https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan . We will post here when the issues have been fixed. * We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is for testing and experimenting only. Anything in there can disappear in a whim. * When we open phabricator.wikimedia.org, the creation of new projects will be still disabled. Existing projects will be able to continue their work, but we are asking new projects to wait a few weeks, until we complete the Bugzilla migration. It's going to be still a bumpy road before Day 1, and we want to control the impact of these disruptions as much as possible. * RT migration will follow. Details will be shared in advance. * Bugzilla migration will follow. Details will be shared in advance as well, but we have a rough idea of the sequence of steps. Details available in the migration plan linked above, pasted here for convenience: 1. Earliest possible/expected date: October 06 but favoring Friday October 10 to interrupt engineering less (starting over the weekend). Bugzilla downtime expected of 1-3 days. Checklist: 2. Instructions to use Phabricator for bug reporting and project management. 3. Documentation of data and features that will not be available in Phabricator after the migration. Phabricator test instance available with a sample of Bugzilla reports imported automatically (say 1 of each 10, about 700 reports). 4. At least one week of margin to receive community feedback and implement improvements. 5. Documentation of the migration process detailing sequence of steps and timeline expected. 6. Go-NoGo meeting with the Phabricator team (Andre, Chase, Mukunda, Quim), Erik, Rob, MarkB, and Greg. Stay tuned. :) Thank you everyone for working on this. The transition cannot happen soon enough, as far as I'm concerned, so these updates are a shining beacon of hope. (I had to switch computers and now git review is completely broken for me, with apparently no fix available. Can we burn gerrit? In a huge fire? Please?) -I ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
Important Phabricator news: A single migration timeline with all the important details is available. https://www.mediawiki.org/wiki/Phabricator#Migration_timeline A video-streamed session The Very Basics of Phabricator is scheduled for Wednesday, September 24. https://plus.google.com/events/c8qe7l0vtf4v6u07k3o059du2lg Registration to phabricator.wikimedia.org is opening for those that really need access to work on any of the existing projects. https://www.mediawiki.org/wiki/Phabricator#Access_to_phabricator.wikimedia.org -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
On Sep 18, 2014 10:19 PM, Daniel Zahn dz...@wikimedia.org wrote:
puppet will make it exec {git_update... .. command = '/usr/bin/git
remote update',
from our gerrit repo. i'm not 100% sure about the sync between
upstream and our gerrit repo, but Chase would know
git remote update doesn't change the working copy. (nor HEAD. i.e. no pull)
but haven't read the manifest myself.
-Jeremy
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
Hi, We have independently tested the third party library for sprint burndown charts that is located here: https://github.com/bluehawk/phabricator-sprint. You can see it here: http://phab.wmflabs.org/burndown/view/1/ Despite being hacked in to the libphutil as a library, though it is phabricator dependent, it works on a basic level. We would require further modification of the code for it to work for us, however. What would it take to get this into the test instance https://phab -01.wmflabs.org/ ? Is this labs test puppet cloning a development repo? Also, how will core and library code changes to phabricator be deployed to the production instance? Where shall we put this phabricator-sprint code so that we can work on it with the intention of having it reviewed and deployed in production as soon as possible? Cheers, Christopher On 18 September 2014 00:09, Daniel Zahn dz...@wikimedia.org wrote: * We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is the puppetized test instance running on the labs puppet master. It is supposed to be as much like production as possible to allow actual testing before making changes in prod. Changes here should be made by uploading puppet changes to the role::phabricator::labs. I would not recommend playing manually with it or soon it will have manual hacks that need to be synced with prod again. It's easy though to spin up phab-02 and how many we like (and there already existed phabricator-test project) where alpha testing can be done manually. you can simply fire up any number of new instances and apply the role, we added it to the wikitech puppet groups list you get when configuring an instance. -- Daniel Zahn dz...@wikimedia.org Operations Engineer ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
I'm very excited to see that you have something working! On Thursday, September 18, 2014, Christopher Johnson christopher.john...@wikimedia.de wrote: Hi, We have independently tested the third party library for sprint burndown charts that is located here: https://github.com/bluehawk/phabricator-sprint. You can see it here: http://phab.wmflabs.org/burndown/view/1/ No we cannot. Anonymous users can't see it (Public policy is missing, I guess), and registration is restricted to @wikimedia.de emails. Despite being hacked in to the libphutil as a library, though it is phabricator dependent, it works on a basic level. We would require further modification of the code for it to work for us, however. What would it take to get this into the test instance https://phab -01.wmflabs.org/ ? Is this labs test puppet cloning a development repo? Also, how will core and library code changes to phabricator be deployed to the production instance? Where shall we put this phabricator-sprint code so that we can work on it with the intention of having it reviewed and deployed in production as soon as possible? -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
Hi, Please check it again. It should be open now. The main open question is Can third-party Phabricator development be staged and tested on labs and then merged into a downstream production repo? Thank you for your help, Christopher On 18 September 2014 13:02, Quim Gil q...@wikimedia.org wrote: I'm very excited to see that you have something working! On Thursday, September 18, 2014, Christopher Johnson christopher.john...@wikimedia.de wrote: Hi, We have independently tested the third party library for sprint burndown charts that is located here: https://github.com/bluehawk/phabricator-sprint. You can see it here: http://phab.wmflabs.org/burndown/view/1/ No we cannot. Anonymous users can't see it (Public policy is missing, I guess), and registration is restricted to @wikimedia.de emails. Despite being hacked in to the libphutil as a library, though it is phabricator dependent, it works on a basic level. We would require further modification of the code for it to work for us, however. What would it take to get this into the test instance https://phab -01.wmflabs.org/ ? Is this labs test puppet cloning a development repo? Also, how will core and library code changes to phabricator be deployed to the production instance? Where shall we put this phabricator-sprint code so that we can work on it with the intention of having it reviewed and deployed in production as soon as possible? -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
On Thursday, September 18, 2014, Christopher Johnson christopher.john...@wikimedia.de wrote: Hi, Please check it again. It should be open now. http://phab.wmflabs.org/burndown/view/1/ 504 Gateway Time-out nginx/1.5.0 The demo effect also seems to work via email... :) The main open question is Can third-party Phabricator development be staged and tested on labs and then merged into a downstream production repo? We haven't defined the process yet, but this is the idea, yes. In fact, it would be better to use https://phab-01.wmflabs.org/ or a clone installed with the same puppet rules, in order to assure that whatever works in the Labs instance will work in the production instance. I proposed a specific plan for this burndown chart feature at https://phabricator.wikimedia.org/T153#15 . Mukunda and Chase are going to be really busy with Day 1 in the next weeks, but maybe you can sync with Yuvi to install burndown in phab-01 and let people test it? If things go well and it works in phab-01, then installing it in phabricator.wikimedia.org shouldn't be a big deal. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
On 09/17/2014 06:09 PM, Daniel Zahn wrote: Changes here should be made by uploading puppet changes to the role::phabricator::labs. I would not recommend playing manually with it or soon it will have manual hacks that need to be synced with prod again. I think he meant end users playing around posting test bugs and such, not sysadmins playing around with one-off hacks. Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
On 09/16/2014 09:34 AM, Quim Gil wrote: 3. Documentation of data and features that will not be available in Phabricator after the migration. Phabricator test instance available with a sample of Bugzilla reports imported automatically (say 1 of each 10, about 700 reports). Presumably you mean 1/100, since we're up to over 70,000 now. Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
On Thu, Sep 18, 2014 at 1:47 AM, Christopher Johnson
christopher.john...@wikimedia.de wrote:
What would it take to get this into the test instance https://phab
-01.wmflabs.org/ ? Is this labs test puppet cloning a development repo?
It uses git::install within puppet.
so for example: git::install { 'phabricator/phabricator':
git::install itself is in modules/git
modules/git/manifests/install.pp:# git::install { 'project/name/on/gerrit':
so it clones from our gerrit installation at
https://gerrit.wikimedia.org/r/#/q/project:phabricator/phabricator,n,z
so what would it take:
- new project/repo created on gerrit
- import code into that repo
- add puppet code that uses git:install to clone from it, copied
from how it does it for the other existing repos
Also, how will core and library code changes to phabricator be deployed to
the production instance?
puppet will make it exec {git_update... .. command = '/usr/bin/git
remote update',
from our gerrit repo. i'm not 100% sure about the sync between
upstream and our gerrit repo, but Chase would know
Where shall we put this phabricator-sprint code so that we can work on it
with the intention of having it reviewed and deployed in production as soon
as possible?
probably into modules/phabricator in repo operations/puppet and
suggest it as a change by uploading into gerrit.
first you could just modify the role::phabricator::labs and after
testing it would be addedi to role::phabricator::main
Chase, correct me if i'm wrong
--
Daniel Zahn dz...@wikimedia.org
Operations Engineer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
I'm happy to hear about RT! And yes, we should have kept the fab domain. בתאריך 16 בספט 2014 16:35, Quim Gil q...@wikimedia.org כתב: Hi, if you were wondering what is going on in Phabricator land... Summary: You can see https://phabricator.wikimedia.org , you can touch https://phab-01.wmflabs.org/ , you will have a chance to provide feedback about the Bugzilla migration before the migration, based on a test instance with a sample of bugs imported. In detail: * https://phabricator.wikimedia.org exists as a read-only instance and it contains the tasks that were migrated from the now decommissioned fab.wmflabs.org. Registration is disabled while we fix some tasks -- details at https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan . We will post here when the issues have been fixed. * We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is for testing and experimenting only. Anything in there can disappear in a whim. * When we open phabricator.wikimedia.org, the creation of new projects will be still disabled. Existing projects will be able to continue their work, but we are asking new projects to wait a few weeks, until we complete the Bugzilla migration. It's going to be still a bumpy road before Day 1, and we want to control the impact of these disruptions as much as possible. * RT migration will follow. Details will be shared in advance. * Bugzilla migration will follow. Details will be shared in advance as well, but we have a rough idea of the sequence of steps. Details available in the migration plan linked above, pasted here for convenience: 1. Earliest possible/expected date: October 06 but favoring Friday October 10 to interrupt engineering less (starting over the weekend). Bugzilla downtime expected of 1-3 days. Checklist: 2. Instructions to use Phabricator for bug reporting and project management. 3. Documentation of data and features that will not be available in Phabricator after the migration. Phabricator test instance available with a sample of Bugzilla reports imported automatically (say 1 of each 10, about 700 reports). 4. At least one week of margin to receive community feedback and implement improvements. 5. Documentation of the migration process detailing sequence of steps and timeline expected. 6. Go-NoGo meeting with the Phabricator team (Andre, Chase, Mukunda, Quim), Erik, Rob, MarkB, and Greg. Stay tuned. :) -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
* We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is the puppetized test instance running on the labs puppet master. It is supposed to be as much like production as possible to allow actual testing before making changes in prod. Changes here should be made by uploading puppet changes to the role::phabricator::labs. I would not recommend playing manually with it or soon it will have manual hacks that need to be synced with prod again. It's easy though to spin up phab-02 and how many we like (and there already existed phabricator-test project) where alpha testing can be done manually. you can simply fire up any number of new instances and apply the role, we added it to the wikitech puppet groups list you get when configuring an instance. -- Daniel Zahn dz...@wikimedia.org Operations Engineer ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
quote name=Quim Gil date=2014-09-16 time=15:34:29 +0200 * We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is for testing and experimenting only. Anything in there can disappear in a whim. Just to be extremely clear: Any data in the new phab-01.wmflabs instance can *and will* disappear when it is no longer needed for testing purposes. We make no commitment to transferring any data out of that instance into the production one. -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator update
We should've kept the fab subdomain ;-) On Sep 16, 2014 8:45 AM, Greg Grossmeier g...@wikimedia.org wrote: quote name=Quim Gil date=2014-09-16 time=15:34:29 +0200 * We have a test instance at https://phab-01.wmflabs.org/ where you can play as much as you want. This instance is for testing and experimenting only. Anything in there can disappear in a whim. Just to be extremely clear: Any data in the new phab-01.wmflabs instance can *and will* disappear when it is no longer needed for testing purposes. We make no commitment to transferring any data out of that instance into the production one. -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
