Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Oleg Piskunov <o.piskunov@tarantool.org>
Cc: tarantool-patches <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v2] gitlab-ci: keep perf results as gitlab-ci artifacts`
Date: Wed, 6 May 2020 21:03:57 +0300	[thread overview]
Message-ID: <20200506180357.gdagxylb4oy67x7q@tkn_work_nb> (raw)
In-Reply-To: <1588786429.441520222@f435.i.mail.ru>

LGTM.

However I would verify it on *-perf branch just in case.

WBR, Alexander Turenko.

On Wed, May 06, 2020 at 08:33:49PM +0300, Oleg Piskunov wrote:
> 
> 
> Gitlab-ci pipeline modified in order to keep
> performance results into gitlab-ci artifacts.
>  
> Closes #4920
>  
> ---
>  
> Github: https://github.com/tarantool/tarantool/tree/opiskunov/gh-4920-perf-artifacts
> Issue: https://github.com/tarantool/tarantool/issues/4920
> 
>  .gitlab-ci.yml | 5 +++++
>  1 file changed, 5 insertions(+)
>  
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index b3b07da..ae2afce 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -93,6 +93,11 @@ variables:
>    stage: perf
>    tags:
>      - docker_perf
> +  artifacts:
> +    when: always
> +    paths:
> +      - "*_result.txt"
> +      - "*_t_version.txt"
>    script:
>      - ${GITLAB_MAKE} perf_run
>  
> --
> 1.8.3.1
>  

  reply	other threads:[~2020-05-06 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 17:33 Oleg Piskunov
2020-05-06 18:03 ` Alexander Turenko [this message]
2020-05-06 20:27   ` Oleg Piskunov
2020-05-07  8:28 ` Sergey Bronnikov
2020-05-08  8:17 ` 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=20200506180357.gdagxylb4oy67x7q@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2] gitlab-ci: keep perf results as gitlab-ci 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