Bug in pushing SNAPSHOT JAR

[wing328]

Description

We found that when the core team opens a PR with a new branch. Travis will deploy the snapshot JAR if the job succeeds, which is not the correct behavior as only the job targeting master should deploy the SNAPSHOT JAR:

[INFO] openapi-generator-project .......................... SUCCESS [  4.929 s]
[INFO] openapi-generator (core library) ................... SUCCESS [ 52.295 s]
[INFO] openapi-generator (executable) ..................... SUCCESS [ 15.301 s]
[INFO] openapi-generator (maven-plugin) ................... SUCCESS [ 11.260 s]
[INFO] openapi-generator-gradle-plugin (gradle-plugin) .... SUCCESS [01:07 min]
[INFO] openapi-generator-online ........................... SUCCESS [ 16.057 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:49 min
[INFO] Finished at: 2018-06-01T08:56:39Z
[INFO] Final Memory: 67M/660M
[INFO] ------------------------------------------------------------------------
Finished mvn clean deploy for master

openapi-generator version

Latest master

Steps to reproduce

Create a branch and open a PR

Suggest a fix/enhancement

https://github.com/OpenAPITools/openapi-generator/blob/master/.travis.yml#L97 is a good starting point.

[jimschubert]

@wing328 this sould be fixed after my release management changes this weekend. I added:

[ "$TRAVIS_PULL_REQUEST" == "false" ]; then

[jmini]

Verified in #285, there is no maven deploy in the travis logs:

• https://api.travis-ci.org/v3/job/390845953/log.txt
• https://api.travis-ci.org/v3/job/390845474/log.txt