mirror of
https://github.com/rbenv/ruby-build.git
synced 2025-07-04 01:11:29 +02:00
According to https://github.com/travis-ci/travis-ci/issues/1719 (closed by https://github.com/travis-ci/travis-core/pull/383), the behavior of $TRAVIS_COMMIT_RANGE should be correct now. We should be able to use it directly.
13 lines
297 B
Bash
Executable file
13 lines
297 B
Bash
Executable file
#!/usr/bin/env bash
|
|
set -e
|
|
|
|
STATUS=0
|
|
bats ${CI:+--tap} test || STATUS="$?"
|
|
|
|
if [ "$TRAVIS_SECURE_ENV_VARS" = "true" ]; then
|
|
./script/mirror update "$TRAVIS_COMMIT_RANGE"
|
|
elif [ "${TRAVIS_PULL_REQUEST:-false}" != "false" ]; then
|
|
./script/mirror verify "$TRAVIS_COMMIT_RANGE"
|
|
fi
|
|
|
|
exit "$STATUS"
|