From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V . Tikhonov" <avtikhon@tarantool.org>,
Oleg Piskunov <o.piskunov@tarantool.org>,
Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] travis-ci: don't deploy 2.5+ pkgs to packagecloud
Date: Wed, 29 Apr 2020 16:05:27 +0300 [thread overview]
Message-ID: <20200429130527.5pqpv5kiakhgamfc@tkn_work_nb> (raw)
In-Reply-To: <eeb3e5caf1a234d4feb430122e5a90f2dc4be213.1588077054.git.alexander.turenko@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.
prev parent reply other threads:[~2020-04-29 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 12:36 Alexander Turenko
2020-04-29 13:05 ` Alexander Turenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200429130527.5pqpv5kiakhgamfc@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=o.piskunov@tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] travis-ci: don'\''t deploy 2.5+ pkgs to packagecloud' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox