Merge branch 'release/3.0.4'

.env

@@ -1,5 +1,3 @@
 # This file is a "template" of which env vars need to be defined for your application
 # Copy this file to .env file for development, create environment variables when deploying to production
 # https://symfony.com/doc/current/best_practices/configuration.html#infrastructure-related-configuration
-SHELL_VERBOSITY=0
-APP_ENV=debug

composer.json

@@ -24,7 +24,8 @@
         "ext-openssl": "*",
         "jakeasmith/http_build_url": "^1.0",
         "padraic/phar-updater": "^1.0",
-        "lesstif/php-jira-rest-client": "^1.35"
+        "lesstif/php-jira-rest-client": "^1.35",
+        "graze/parallel-process": "^0.8.1"
     },
     "require-dev": {
         "symfony/phpunit-bridge": "^2.8|^3|^4.1",

docs/docs/available-tasks.md

@@ -521,7 +521,8 @@ phab --config=<config> notify <message> <channel>
 This command will send the notification <message> to Mattermosts channel <channel>. For a detailed description have a look into the dedicated documentation.
 
 **Examples**
-* `phab config:mbb notify "hello world" "off-topic": sends `hello world` to `#off-topic`
+
+* `phab config:mbb notify "hello world" "off-topic"`: sends `hello world` to `#off-topic`
 
 ## app:scaffold
 

docs/docs/configuration.md

@@ -197,6 +197,10 @@ This will print all host configuration for the host `staging`.
     * `name` contains the name of the docker-container. This is needed to get the IP-address of the particular docker-container when using ssh-tunnels (see above).
     * for docker-compose-base setups you can provide the `service` instead the name, phabalicious will get the docker name automatically from the service.
 
+### Configuration of the mattermost-method
+
+* `notifyOn`: a list of all tasks where to send a message to a Mattermost channel. Have a look at the global Mattermost-configuration-example below.
+
 ### dockerHosts
 
 `dockerHosts` is similar structured as the `hosts`-entry. It's a keyed lists of hosts containing all necessary information to create a ssh-connection to the host, controlling the docker-instances, and a list of tasks, the user might call via the `docker`-command. See the `docker`-entry for a more birds-eye-view of the concepts.
@@ -321,6 +325,37 @@ jira:
   projectKey: <jira project-key>
 ```
 
+### mattermost
+
+Phabalicious can send notifications to a running Mattermost instance. You need to create an incoming web hook in your instance and pass this to your configuration. Here's an example
+
+```
+mattermost:
+  username: phabalicious
+  webhook: https://chat.your.server.tld/hooks/... 
+  Channel: "my-channel"
+
+hosts:
+  test:
+    needs:
+      - mattermost
+    notifyOn:
+      - deploy
+      - reset
+```
+
+* `mattermost` contains all global mattermost config.
+    * `username` the username to post messages as
+    * `webhook` the address of the web-hook
+    * `channel` the channel to post the message to
+* `notifyOn` is a list of tasks which should send a notification
+
+You can test the Mattermost config via
+
+```
+phab notify "hello world" --config <your-config>
+```
+
 ### other
 
 * `deploymentModule` name of the deployment-module the drush-method enables when doing a deploy