Code cov on releases

[TimvdLippe]

Releases are now triggering CI builds to generate the code coverage reports.
An example of a normal build can be found at https://travis-ci.org/mockito/mockito/builds/143765346#L334-L374
An example of a build ignored as the commit message contained [ci skip-release] can be found at https://travis-ci.org/mockito/mockito/builds/143765834#L311-L314

Fixes #465

[codecov-io]

Current coverage is 87.87%

No coverage report found for master at 5dd0f71.

Powered by Codecov. Last updated by 5dd0f71...8916088

[bric3]

This can be a oneliner I believe

if [[ $(git log --format=%B -n 1) != *"[ci skip-release]"* ]] ; then ./gradlew release; fi

[TimvdLippe]

The git log command was from a travis issue as there is an intent to add the new environment variable. The command is kinda magic, so naming the variable makes it imo easier to comprehend.

[bric3]

From the changes I don't understand why the code coverage is mentioned in this PR. Code coverage should be triggered by any travis build.

[TimvdLippe]

Yes it is triggered on every Travis build. However, as explained in #465 the delivery drones creates a release commit with ci skip. Therefore Travis is not triggered and codecov fails, see the first comment on this PR.

To prevent a release loop on travis, instead of a full ci skip it only does a ci skip-release. This is handled in the .travis.yml.

[raphw]

Is this PR still relevant? If yes, is it ready to be merged?

[TimvdLippe]

Yes it is still relevant. Releases do not trigger code cov and therefore result in empty comparisons.

[TimvdLippe]

I will merge it, if it seems to break stuff (I do not expect it to) then I will revert.

[mureinik]

@TimvdLippe continuing our discussion on PR #980 - can this fix be backported to release/2.x? IIUC, the majority of the work is done there, and CodeCov will be very helpful there too.

[TimvdLippe]

@mureinik Back then we did not divert yet with release/2.x so I think it recently regressed in release/2.x instead. Have to investigate :(