Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>,
	tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2] gitlab-ci: adjust base URL of RPM/Deb repositories
Date: Fri, 21 Feb 2020 15:52:10 +0300	[thread overview]
Message-ID: <20200221125210.3niqrv5y62fmukpo@tkn_work_nb> (raw)
In-Reply-To: <511105ff6a6a547a85efe4343c2dbed79fc04609.1582116829.git.avtikhon@tarantool.org>

LGTM.

I didn't test it manually and hope that you already performed proper
testing of the change.

Pushed to master, 2.3, 2.2, 2.1 and 1.10.

CCed Kirill.

WBR, Alexander Turenko.

On Wed, Feb 19, 2020 at 03:56:35PM +0300, Alexander V. Tikhonov wrote:
> Our S3 based repositories now reflect packagecloud.io repositories
> structure.
> 
> It will allow us to migrate from packagecloud.io w/o much complicating
> redirection rules on a web server serving download.tarantool.org.
> 
> Deploy source packages (*.src.rpm) into separate 'SRPM' repository
> like packagecloud.io does.
>
> Changed repository signing key from its subkey to public and moved it
> to gitlab-ci environment.
> 
> Follows up #3380
> ---
> 
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-3380-rpm-packages-paths-full-ci
> Issue: https://github.com/tarantool/tarantool/issues/3380
> 
>  tools/update_repo.sh | 66 ++++++++++++++++++++++++--------------------
>  1 file changed, 36 insertions(+), 30 deletions(-)

  reply	other threads:[~2020-02-21 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 12:56 Alexander V. Tikhonov
2020-02-21 12:52 ` Alexander Turenko [this message]
2020-02-21 21:49 ` Alexander Turenko
  -- strict thread matches above, loose matches on Subject: below --
2020-02-19 11:47 Alexander V. Tikhonov

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=20200221125210.3niqrv5y62fmukpo@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2] gitlab-ci: adjust base URL of RPM/Deb repositories' \
    /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