summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
diff options
context:
space:
mode:
authordrebs <drebs@leap.se>2017-07-07 20:05:39 -0300
committerdrebs <drebs@leap.se>2017-07-08 08:05:24 -0300
commit3b51520b4be2f48a204bc0d630c88058ed51afa9 (patch)
tree34c1948df1461a33ecf15f858553ddc18d76b437 /.gitlab-ci.yml
parentf21d9e1a4e6d0a2ed6d7af83191e39a2a883241b (diff)
[benchmark] setup env for benchmark-all-commits conditionally
Diffstat (limited to '.gitlab-ci.yml')
-rw-r--r--.gitlab-ci.yml25
1 files changed, 1 insertions, 24 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 731c5da6..0b7510c5 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -66,33 +66,10 @@ benchmark:
- benchmark
services:
- couchdb
- allow_failure: true
script:
- # By default, gitlab-runner will checkout in a detached HEAD
- # (see https://gitlab.com/gitlab-org/gitlab-ce/issues/19421)
- # We want pytest-benchmark to report the proper branch name,
- # so we make sure we stay at the current branch.
- # Also, variable names have changed in latest version of gitlab,
- # but the doc seems to be outdated (see also
- # https://docs.gitlab.com/ce/ci/variables/README.html).
- - git checkout -B "$CI_COMMIT_REF_NAME" "$CI_COMMIT_REF"
- # Gitlab will checkout current revision as master / origin/master
- # We need some files from the "furure" in order to post the right
- # benchmarking data to elasticsearch.
- - git remote add leap https://leap.se/git/soledad
- - git fetch leap
- - git checkout leap/master
- testing/tox.ini
- testing/tests/benchmarks/conftest.py
- testing/tests/conftest.py
- testing/check-pysqlcipher.py
- - git checkout leap/benchmark-all-commits scripts/benchmark/tune-adbapi-parameters.sh
- # ensure larger timeout and more retries for async/concurrent sqlcipher access
- - ./scripts/benchmark/tune-adbapi-parameters.sh
- - git status
- - git show -s --pretty=fuller
- cd testing
- curl -s couchdb:5984
+ - '[ -n "${BENCHMARK_ALL_COMMITS}" ] && ./scripts/benchmark/setup-all-commits-env.sh'
# You can provide a $NETRC variable containing the creds for your
# elasticsearch instance so it's protected from being leaked in the
# CI console