From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (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 48B25469719 for ; Fri, 21 Feb 2020 15:38:23 +0300 (MSK) Date: Fri, 21 Feb 2020 15:38:42 +0300 From: Alexander Turenko Message-ID: <20200221123842.26d4p5z3b5ky6xea@tkn_work_nb> References: <20200218214130.h2wilrsmf2zaku25@tkn_work_nb> <1582090633.801050394@f349.i.mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1582090633.801050394@f349.i.mail.ru> Subject: Re: [Tarantool-patches] [PATCH v4] Implement perf testing at gitlab-ci List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Tikhonov Cc: Oleg Piskunov , tarantool-patches@dev.tarantool.org > >Don't sure how it should look at other release branches: > > > >- Whether something need to be changed for 2.3/2.2? > >  - perf_only_template should have "2.3" / "2.2" branch instead of > >    master, that I understood. > Right, that is the only change. Pushed to 2.3 and 2.2. > Right, it needs special Dockerfile w/o SQL benchmarks, I already have > separate 'avtikhon/gitlab-ci_1.10-perf' branch for it, I'll update it with changes > from the current commit. Pushed to 1.10.