Figure out what to do when there are multiple jobs in a single Travis run

[marco-c]

The after_success script is executed for each job (e.g. each Node.js version specified in .travis.yml), which means auto-deploy is executed multiple times.

[marco-c]

For example: https://travis-ci.org/marco-c/oghliner/builds/85635318

Travis logs for the two builds:
log1.txt
log2.txt

[marco-c]

One possible solution would be to parse the .travis.yml and only run deploy on Travis if the Node.js version which is running the script is the newest one specified in .travis.yml.

[marco-c]

One possible solution would be to parse the .travis.yml and only run deploy on Travis if the Node.js version which is running the script is the newest one specified in .travis.yml.

Actually, this isn't a viable solution. There are many variables that could make Travis spin multiple jobs per build.

[mykmelez]

See travis-ci/travis-ci#929 for the Travis feature request.

[mykmelez]

Per that issue, this script might help:

https://github.com/dmakhno/travis_after_all