Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 1/2] build: update rules for extended CI
Date: Fri, 22 Mar 2019 14:51:02 +0300	[thread overview]
Message-ID: <20190322115101.lidrvdftwepjlcly@tkn_work_nb> (raw)
In-Reply-To: <20190322084106.vsxeuoe73ob6wgeh@tarantool.org>

On Fri, Mar 22, 2019 at 11:41:06AM +0300, Kirill Yukhin wrote:
> Hello,
> 
> On 21 Mar 16:25, Kirill Yukhin wrote:
> > Development branch is now named master, so
> > update conditions for exetended extended checks on
> > Travis.
> > Also, set new repo name.
> 
> Fixed typo, set repo to 2_2 and committed to master.

Tarballs problem is not fixed (see my previous email). 2_2 repository is
created but CI fails (maybe the push was before the bucket creation).

download.tarantoo.io is not set up to redirect to packagecloud.

> 
> --
> Regards, Kirill Yukhin
> 

  reply	other threads:[~2019-03-22 11:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 13:25 [tarantool-patches] [PATCH 0/2] build: update rules for master branch Kirill Yukhin
2019-03-21 13:25 ` [tarantool-patches] [PATCH 1/2] build: update rules for extended CI Kirill Yukhin
2019-03-22  0:44   ` [tarantool-patches] " Alexander Turenko
2019-03-22  8:41   ` Kirill Yukhin
2019-03-22 11:51     ` Alexander Turenko [this message]
2019-03-22 15:22       ` Kirill Yukhin
2019-03-22 15:36         ` Alexander Turenko
2019-03-21 13:25 ` [tarantool-patches] [PATCH 2/2] build: set specific name for packages of master branch Kirill Yukhin
2019-03-21 14:09   ` [tarantool-patches] " Kirill Yukhin
2019-03-21 14:21     ` Konstantin Osipov
2019-03-21 15:20       ` Kirill Yukhin

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=20190322115101.lidrvdftwepjlcly@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=kyukhin@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 1/2] build: update rules for extended CI' \
    /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