On CI container slaves, I suggest, we disable XDebug by default, and wrap phpunit to use a configuration file with XDebug:

@Sandlayth created an account to fire notifications to our Mailgun domain, I created a route, so all is configured from our side.

Per T984.

We'll start with inline JSON and we'll advise when new formats pop. JSON is more and more universal.

Needed at operations level by D372.

Per D629, groupsMapping / projectsMapping / repositoryMapping becomes map, to get a common basis.

Current status: we've all the code ready.

Next step is to provide a configuration with:

• the mapping job/project
• emulate what we would need at Jenkins plugin level: only fire notifications on job failed

According Bradipo from Freenode tcl channel, parsing is okay (and produces a correct dict) with json 1.3.3.

JSON makes a lot of sense, there is no need to parse twice a JSON payload, once for our notification format, once for the source payload.

According Bradipo from TCL, parsing is okay (and produces a correct dict) with json 1.3.3.

According Bradipo from TCL, parsing is okay (and produces a correct dict) with json 1.3.3.

Currently, D347 is, as far as I know, the first piece of code consuming raw content.

The error occurs at the JSON parser level, invoked by json::json2dict $payload in get_image_from_docker_payload proc.

Rebased against master.

The payload contains a scm section.

An example of notifications for one of our Jenkins job is at P212.