Readd Travis support and update documentation

[ottlinger]

#29

Provide example .travis.yml to verify Travis integration.

[haffla]

The project was migrated from Travis to Circle. See f9eaf75

I don't think this is the problem

[rtfpessoa]

After you commit something new, check the build here: https://travis-ci.org/codacy/php-codacy-coverage

[rtfpessoa]

Can you update the travis file to look like the one pointed by @haffla ?

Something like:

script:
   - php vendor/bin/phpunit
 
 after_script:
   - php bin/codacycoverage clover

[haffla]

Please see my latest comment in #29

[haffla]

@ottlinger I don't really understand the aim of your PR. The CODACY_PROJECT_TOKEN is your secret API token and should not go into version control. You should add this env variable in Travis where only you can see it.

And why is travis_retry necessary?

[ottlinger]

@haffla The travis build does not fail anymore, but no coverage results are transferred to Codacy without the API key. Since the documentation does not say how this key is configured in Travis I've added that part.

Travis_retry is the recommended way to do things if relying on external stuff:
https://docs.travis-ci.com/user/common-build-problems/#My-builds-are-timing-out

[rtfpessoa]

This is needs to be private. In circle ci they have a way to add it in the UI in travis they must have something similar.

[ottlinger]

I've updated the documentation - thanks.
Since I've experienced build timeouts I'm in favour of keeping the retry option as it's recommended by Travis and prevents users from searching for it separately.

[haffla]

Sensible information like API keys should be made env vars as described here https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings.

Regarding travis-retry, I don't see the need as long as one does not experience timeouts.

[ottlinger]

@rtfpessoa would you mind accepting the PR after I've applied the changes? Thanks.

[rtfpessoa]

I also do not think travis_retry is a nice to have. People will just use it blindly and with no idea what it does.

[rtfpessoa]

The readme is still wrong. Sorry for te trouble the idea is just to have it as simple as possible.

[ottlinger]

@rtfpessoa sorry - corrected again.

[rtfpessoa]

LGTM 👍

Also, thanks for the help @haffla

[haffla]

Cheers Rodrigo, hope to see you soon! Say hello to everyone @codacy ;)

[rtfpessoa]

Everyone here sends their best regards. Any plans to visit Lisbon?

[haffla]

Quite likely this year, but nothing planned yet. Man what I miss most is that place where you always have lunch... the foooood. Hehehe see you!