Четверг, 14 мая 2020, 13:29 +03:00 от Alexander V. Tikhonov <avtikhon@tarantool.org>:
 

Release branches should be regularly run using gitlab-ci pipeline
schedules:
  https://gitlab.com/tarantool/tarantool/pipeline_schedules
It will help to detect flaky issues. But there is no need to rerun
too long running performance testing, to block it in schedules the
option 'schedules' in 'except:' field was set.

Part of #4974
---

Github: https://github.com/tarantool/tarantool/tree/avtikhon/schedule_except_perf
Issue: https://github.com/tarantool/tarantool/issues/4974

 .gitlab-ci.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index c7f58b98d..256b368c4 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -32,6 +32,8 @@ variables:
   only:
     - master
     - /^.*-perf$/
+ except:
+ - schedules
   variables: &perf_vars_definition
     IMAGE_PERF: "${CI_REGISTRY}/${CI_PROJECT_PATH}/perf/ubuntu-bionic:perf_master"
     IMAGE_PERF_BUILT: "${CI_REGISTRY}/${CI_PROJECT_PATH}/perf_tmp/ubuntu-bionic:perf_${CI_COMMIT_SHORT_SHA}"
--
2.17.1