tarantool / tarantool/tarantool

infra: verify RPM / Deb repositories, packages and tarballs

Open
#5,512 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

infrastructure qa
Dominant language
Lua
Stars
3.7k
Forks
419
Avg merge
1d 23h
Merged PRs (30d)
88

Description

Tarantool version: 2.7.0-30-g62dffc7eb.

We have infrastructure for delivering RPM / Deb packages to users. However it is not verified at all. We should regularly verify the following points:

  • A repository can be enabled successfully using the instructions on our website.
  • After enabling of the repository a package can be successfully installed.
  • Source tarballs for tarantool are downloadable via download.tarantool.org.
  • The listing of the source tarballs is available on download.tarantool.org.

The repositories are determined by the following matrix:

  • Tarantool release series: 1.10, 2.1, 2.2, etc.
  • The repository type: live / release.
  • Linux distribution + the distribution version: Debian (8, 9, 10), Ubuntu (...), CentOS (6, 7, 8), Fedora (...).

The packages are:

  • Tarantool itself.
  • Modules and connectors (see some minimal list in #5265).

Related: TNT-53.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository instructions at https://tarantool.io/en/download/, the minimal module list in #5265, and the related TNT-53 work. Define coverage for each release, repository type, distribution, and package before implementing recurring checks; done means repository enablement, package installation, and source-tarball download and listing are verified.

Written by the indexing model from the issue text.

Assessment

Domain
devops, infrastructure, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.