Config to deploy script
=======================

(c) 2015, 2016,  Sébastien Santoro aka Dereckson
Released under BSD license.

This script reads the Wikimedia-Site-Requests project board on Phabricator
and queries Gerrit to get information about open changes.

It requires PhantomJS 2.x to scrape Phabricator board.
Ubuntu Trusty package is with PhantomJS 1.9.0 and not supported by this tool.

It then prints the lines of changes to deploy, ready to add to our wiki page
https://wikitech.wikimedia.org/wiki/Deployments.

To run it, `bin/todeploy` or `php src/todeploy.php`.

To customize it, start by the $config array around line 10 of this file.

______________________________________________________________________________

[FAQ]

Q. How to use it for another project?

A. Create a column 'To deploy', get the board number and edit config array.

* * *

Q. How to generate the list from another column than 'To deploy'?

A. Add to $config 'PhabricatorBoardColumn' => 'Your column name'

* * *

Q. Why do you scrape Phabricator instead to query conduit?

A. Currently, there is no straightforward way to get this information through
conduit. For more information, see https://secure.phabricator.com/T5523.

* * *

Q. Can I use it for other software?

* If you use Bugzilla or other bug tracker with Gerrit, get an array with the
  bug number, and pass it to the ChangesToDeploy constructor.

* If you use purely Phabricator, keep the PhabricatorBoardScraper part and then
  check for every task if an accepted differential is attached with a call to
  maniphest.gettasktransactions Phabricator API.

* If you use Phabricator, then another product, the PhabricatorBoardScraper
  GetTasksId method will give you an array of the tasks to deploy. You need
  a reference into your product to these tasks. Then query your application.