From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp51.i.mail.ru (smtp51.i.mail.ru [94.100.177.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 086D1469710 for ; Thu, 14 May 2020 13:29:40 +0300 (MSK) From: "Alexander V. Tikhonov" Date: Thu, 14 May 2020 13:29:38 +0300 Message-Id: <2ad8677044f4a2eac3ec7ae3479dbebe09ea3f15.1589452096.git.avtikhon@tarantool.org> Subject: [Tarantool-patches] [PATCH v1] gitlab-ci: disable perf tesing in schedulled runs List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Oleg Piskunov , Sergey Bronnikov Cc: tarantool-patches@dev.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