[CI] Leverage after_success phase in .travis.yml

There were two `ls -l dnscrypt-proxy-*.tar.gz dnscrypt-proxy-*.zip`
commands in `.travis.yml`, one in the `script`(build) phase, one in the
`after_deploy` phase, they were actually duplicated.

As deployment job won't create any new files, and the command isn't part
of the steps to build artifacts, but to confirm/list the built files,
this action looks more suitable to be placed in the `after_success`, to
be separated with the build commands, and the duplicated one in the
`after_deploy` phase could be removed.
This commit is contained in:
Peter Dave Hello 2019-08-07 21:07:58 +08:00 committed by Frank Denis
parent 39821afd11
commit bf32a9b8c5

View File

@ -191,6 +191,7 @@ script:
- cp ../LICENSE example-dnscrypt-proxy.toml example-*.txt android-x86_64/
- zip -9 -r dnscrypt-proxy-android_x86_64-${TRAVIS_TAG:-dev}.zip android-x86_64
after_success:
- ls -l dnscrypt-proxy-*.tar.gz dnscrypt-proxy-*.zip
deploy:
@ -225,9 +226,6 @@ before_deploy:
- echo "$MINISIGN_SK" >> /tmp/minisign.key
- echo | minisign -s /tmp/minisign.key -Sm dnscrypt-proxy-*.tar.gz dnscrypt-proxy-*.zip
after_deploy:
- ls -l dnscrypt-proxy-*.tar.gz dnscrypt-proxy-*.zip
before_install:
- NDK_VER=r18
- curl -LO http://dl.google.com/android/repository/android-ndk-${NDK_VER}-linux-x86_64.zip