make build artifacts accessable

[Flyingmana]

see: http://docs.travis-ci.com/user/uploading-artifacts/

Reason:
You run several static analyzers like for example the phpcs part.
This generates a report file if it fails. It would be helpfull if people can look into this somehow, for example trough the linked travis feature.

[verklov]

Hello @Flyingmana! We already had a request that you mention about. It is contained in the comments to #926. We created a ticket in the backlog for this improvement MAGETWO-32786. The team will work on this according to the priorities.

According to the new procedure of working with GitHub improvements and feature requests, we are closing GitHub tickets once we have a ticket in the backlog created in internal tracker. Thank you for your request! We are closing this ticket now. Please watch the repository updates.

[piotrekkaminski]

Thank you for your submission.

We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues.

Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

We are closing this GitHub ticket and have moved your request to the new forum.

[magento-engcom-team]

Hi @Flyingmana. Thank you for your report.
The issue has been fixed in magento/graphql-ce#990 by @TomashKhamlai in 2.3-develop branch
Related commit(s):

• bccd2877b6d42ff9860437426e1cf97509695d35

The fix will be available with the upcoming 2.3.4 release.