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 v10] gitlab-ci: push Deb/RPM packages to S3 based repos
Date: Tue, 4 Feb 2020 10:52:05 +0300 [thread overview]
Message-ID: <20200204075204.fc7hvu6gi7qco37m@tkn_work_nb> (raw)
In-Reply-To: <6053f76b5c8fd80df91392f7a02b61c47006e341.1580793835.git.avtikhon@tarantool.org>
Pushed to master, 2.3, 2.2, 2.1 (w/o Fedora 31), 1.10.
CCed Kirill.
I'll file an issue for follow up activities.
WBR, Alexander Turenko.
On Tue, Feb 04, 2020 at 08:37:50AM +0300, Alexander V. Tikhonov wrote:
> We're going to use S3 compatible storage for Deb and RPM repositories
> instead of packagecloud.io service. The main reason is that
> packagecloud.io provides a limited amount of storage, which is not
> enough for keeping all packages (w/o regular pruning of old versions).
>
> Note: At the moment packages are still pushed to packagecloud.io from
> Travis-CI. Disabling this is out of scope of this patch.
>
> This patch implements saving of packages on an S3 compatible storage and
> regeneration of a repository metadata.
>
> The layout is a bit different from one we have on packagecloud.io.
>
> packagecloud.io:
>
> | - 1.10
> | - 2.1
> | - 2.2
> | - ...
>
> S3 compatible storage:
>
> | - live
> | - 1.10
> | - 2.1
> | - 2.2
> | - ...
> | - release
> | - 1.10
> | - 2.1
> | - 2.2
> | - ...
>
> Both 'live' and 'release' repositories track release branches (named as
> <major>.<minor>) and master branch. The difference is that 'live' is
> updated on every push, but 'release' is only for tagged versions
> (<major>.<minor>.<patch>.0).
>
> Packages are also built on '*-full-ci' branches, but only for testing
> purposes: they don't pushed anywhere.
>
> The core logic is in the tools/update_repo.sh script, which implements
> the following flow:
>
> - create metadata for new packages
> - fetch relevant metadata from the S3 storage
> - push new packages to the S3 storage
> - merge and push the updated metadata to the S3 storage
>
> The script uses 'createrepo' for RPM repositories and 'reprepro' for Deb
> repositories.
>
> Closes #3380
> ---
>
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-3380-push-packages-s3-full-ci
> Issue: https://github.com/tarantool/tarantool/issues/3380
next prev parent reply other threads:[~2020-02-04 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 5:37 Alexander V. Tikhonov
2020-02-04 7:52 ` Alexander Turenko [this message]
2020-02-04 8:38 ` Alexander Turenko
-- strict thread matches above, loose matches on Subject: below --
2020-02-03 14:44 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=20200204075204.fc7hvu6gi7qco37m@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 v10] gitlab-ci: push Deb/RPM packages to S3 based repos' \
/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