On Sat, Aug 27, 2016 at 7:00 PM, Bryan Davis <[email protected]> wrote: > On Sat, Aug 27, 2016 at 4:40 PM, Bryan Davis <[email protected]> wrote: >> On Sat, Aug 27, 2016 at 1:50 PM, Magnus Manske >> <[email protected]> wrote: >>> Should existing, third-party repos be tracked in toolsadmin and/or >>> Phabricator/Differential? >> >> I have (undocumented) plans to add support for editing and publishing >> toolinfo.json compatible descriptions for each tool. When this is >> implemented it will support connecting 3rd party hosting to each tool. >> >> Right now it is possible to create a Diffusion repo through the admin >> console and then manually set it up as a mirror of an existing GitHub >> repo through the management interface in Phabricator. Kunal managed to >> do this with one of his tools [R1947]. Currently the configuration of >> Phabricator itself only allows connecting to GitHub, but we have one >> bug open to allow another external host. I expect as we talk through >> the reasonable solutions of that issue that we will either open up to >> a slightly larger fixed whitelist and come up with a procedure for >> adding more, or determine that automatic external mirroring is >> undesirable. If the answer ends up being that Wikimedia can't allow >> their main Phabricator to connect to arbitrary 3rd party hosts to >> mirror into Diffusion, I think someone can whip up a tool that can >> poll, fetch and push to manage mirrors for interested tools in a >> weekend. :) > > Related to this, if anyone has a Tool with an existing repository that > is hosted in Diffusion (either directly or mirrored from Gerrit), feel > free to open a ticket in the #Striker project asking to have it > connected with your tool. I can manually alter the permissions on the > Phabricator side to match what the admin console would do for a new > repo and register it with the application's tracking database. I > thought about making some UI for this in the app itself, but decided > that the number of affected users was small enough that I could just > handle it directly instead of introducing clutter. > > h/t to Luke081515 for bringing this topic up on irc to prompt this addendum
I just added a short how-to on using the Phabricator UI to setup a new Diffusion repository as a mirror of a GitHub repo. Eventually I'd like to make this native functionality in Striker [1]. I also did a deploy today that includes fixes for seven bugs [2] that had been found since launch. Keep the bug reports & feature requests coming! [0]: https://wikitech.wikimedia.org/wiki/Toolsadmin.wikimedia.org/FAQ [1]: https://phabricator.wikimedia.org/T143971 [2]: https://wikitech.wikimedia.org/wiki/Toolsadmin.wikimedia.org/Deployments#2016-08-29 Bryan -- Bryan Davis Wikimedia Foundation <[email protected]> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA irc: bd808 v:415.839.6885 x6855 _______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
