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 dzahn@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 dzahn@wikimedia.org Operations Engineer
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l