From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp53.i.mail.ru (smtp53.i.mail.ru [94.100.177.113]) (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 3D1E54696C3 for ; Wed, 29 Apr 2020 16:05:37 +0300 (MSK) Date: Wed, 29 Apr 2020 16:05:27 +0300 From: Alexander Turenko Message-ID: <20200429130527.5pqpv5kiakhgamfc@tkn_work_nb> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH] travis-ci: don't deploy 2.5+ pkgs to packagecloud List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Alexander V . Tikhonov" , Oleg Piskunov , Sergey Bronnikov Cc: tarantool-patches@dev.tarantool.org On Tue, Apr 28, 2020 at 03:36:44PM +0300, Alexander Turenko wrote: > Now we have S3 based infrastructure for RPM / Deb packages and GitLab CI > pipelines, which deploys packages to it. > > We don't plan to add 2.5+ repositories on packagecloud.io, so instead of > usual change of target bucket from 2_N to 2_(N+1), the deploy stage is > removed. > > Since all distro specific jobs are duplicated in GitLab CI pipelines and > those Travis-CI jobs are needed just for deployment, it worth to remove > them too. > > Follows up #3380. > Part of #4947. > --- > > Kirill, please, review the deprecation plan in the issue. This patch is > the first one that follows on this plan. > > Alexander, Oleg, Sergey I hope you're okay with the plan (we discussed > something like this), but please let me know if something doubt you. > > https://github.com/tarantool/tarantool/issues/4947 > https://github.com/tarantool/tarantool/tree/Totktonada/gh-4947-stop-deploy-to-packagecloud > > .travis.yml | 73 ----------------------------------------------------- > 1 file changed, 73 deletions(-) Pushed to master in 2.5.0-12-gba206b484.