From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alexander.turenko@tarantool.org>
Received: from smtpng1.m.smailru.net (smtpng1.m.smailru.net [94.100.181.251])
 (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 0B56046970E
 for <tarantool-patches@dev.tarantool.org>;
 Mon,  3 Feb 2020 16:42:14 +0300 (MSK)
Date: Mon, 3 Feb 2020 16:42:26 +0300
From: Alexander Turenko <alexander.turenko@tarantool.org>
Message-ID: <20200203134225.r7ptxf7shhzbhozg@tkn_work_nb>
References: <5c7b8f38b3d67bd79b129f46be4aeed4d709f15a.1580581971.git.avtikhon@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <5c7b8f38b3d67bd79b129f46be4aeed4d709f15a.1580581971.git.avtikhon@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v9] gitlab-ci: push Deb/RPM packages
	to S3 based repos
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>, tarantool-patches@dev.tarantool.org

> S3 compatible storage:
> 
>  | - live
>  | - 1.10
>  | - 2.1
>  | - 2.2
>  | - ...
>  | - release
>  | - 1.10
>  | - 2.1
>  | - 2.2
>  | - ...

Please, format it as a tree:

 | - live
 |   - 1.10

And so on.

> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 3af5a3c8a..8d2a15ce8 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -8,9 +8,24 @@ variables:
>  
>  .release_only_template: &release_only_definition
>    only:
> -    refs:
> -      - master
> -      - /^.*-full-ci$/
> +    - master

It is almost same as &deploy_only_definition below. I don't found strict
correspondence between templates and different kinds of jobs we have.
Looks messy...

> +
> +.fullci_only_template: &fullci_only_definition
> +  only:
> +    - /^.*-full-ci$/

It is not used anywhere.