Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org,
	Alexander Turenko <alexander.turenko@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v3] gitlab-ci: save failed test results artifacts
Date: Fri, 25 Sep 2020 18:48:09 +0300	[thread overview]
Message-ID: <20200925154809.wtuod22cvgy7y2r2@tarantool.org> (raw)
In-Reply-To: <faa2b6814dc8683935c6b42c8857ea6ba642781f.1600843050.git.avtikhon@tarantool.org>

Hello,

On 23 сен 09:40, Alexander V. Tikhonov wrote:
> Added artifacts saver to all gitlab-ci jobs with testing.
> 
> Gitlab-ci jobs saves its results files in the following paths:
> 
>   1. base jobs for testing different features:
>     - test/var/artifacts
> 
>   2. OSX jobs:
>     - ${OSX_VARDIR}/artifacts
> 
>   3. pack/deploy jobs:
>     - build/usr/src/*/tarantool-*/test/var/artifacts
> 
>   4. VBOX jobs (freebsd_12) on virtual host:
>     - ~/tarantool/test/var/artifacts
> 
> In gitlab-ci configuration added 'after_script' section with script
> which collects from different test places 'artifacts' directories
> created by test-run tool. It saves 'artifacts' directories as root
> path in artifacts packages. User will be able to download these
> packages using gitlab-ci GUI either API.
> 
> Additionally added OSX_VARDIR environment variable to be able to
> setup common path for artifacts and OSX shell scripts options.
> 
>   OSX_VARDIR: /tmp/tnt
> 
> Part of #5050

I've checked your patch into 1.10, 2.4, 2.5 and master.

--
Regards, Kirill Yukhin

      parent reply	other threads:[~2020-09-25 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  6:40 Alexander V. Tikhonov
2020-09-24  3:40 ` Alexander Turenko
2020-09-24  4:24   ` Alexander V. Tikhonov
2020-09-25 15:48 ` Kirill Yukhin [this message]

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=20200925154809.wtuod22cvgy7y2r2@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v3] gitlab-ci: save failed test results artifacts' \
    /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