Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
To: "Олег Пискунов" <o.piskunov@corp.mail.ru>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>,
	tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1] Keep perf results as gitlab-ci artifacts
Date: Thu, 30 Apr 2020 10:32:26 +0300	[thread overview]
Message-ID: <20200430073226.GA26217@hpalx> (raw)
In-Reply-To: <1587974039.618638020@f133.i.mail.ru>

Hi Oleg, thanks for the patch, LGTM, please proceed to Kirill to push.

On Mon, Apr 27, 2020 at 10:53:59AM +0300, Олег Пискунов 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 | 43 +++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 43 insertions(+)
>  
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index fd265aa..4b05fa5 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -201,12 +201,22 @@ perf_sysbench:
>    variables:
>      <<: *perf_vars_definition
>      BENCH: 'sysbench'
> +  artifacts:
> +    when: always
> +    paths:
> +      - Sysbench_result.txt
> +      - Sysbench_t_version.txt
>  
>  perf_tpcc:
>    <<: *perf_docker_test_definition
>    variables:
>      <<: *perf_vars_definition
>      BENCH: 'tpcc'
> +  artifacts:
> +    when: always
> +    paths:
> +      - tpc.c_result.txt
> +      - tpc.c_t_version.txt
>  
>  perf_ycsb_hash:
>    <<: *perf_docker_test_definition
> @@ -214,6 +224,11 @@ perf_ycsb_hash:
>      <<: *perf_vars_definition
>      BENCH: 'ycsb'
>      ARG: 'hash'
> +  artifacts:
> +    when: always
> +    paths:
> +      - ycsb.hash_result.txt
> +      - ycsb.hash_t_version.txt
>  
>  perf_ycsb_tree:
>    <<: *perf_docker_test_definition
> @@ -221,6 +236,11 @@ perf_ycsb_tree:
>      <<: *perf_vars_definition
>      BENCH: 'ycsb'
>      ARG: 'tree'
> +  artifacts:
> +    when: always
> +    paths:
> +      - ycsb.tree_result.txt
> +      - ycsb.tree_t_version.txt
>  
>  perf_nosqlbench_hash:
>    <<: *perf_docker_test_definition
> @@ -228,6 +248,11 @@ perf_nosqlbench_hash:
>      <<: *perf_vars_definition
>      BENCH: 'nosqlbench'
>      ARG: 'hash'
> +  artifacts:
> +    when: always
> +    paths:
> +      - nosqlbench.hash_result.txt
> +      - nosqlbench.hash_t_version.txt
>  
>  perf_nosqlbench_tree:
>    <<: *perf_docker_test_definition
> @@ -235,12 +260,25 @@ perf_nosqlbench_tree:
>      <<: *perf_vars_definition
>      BENCH: 'nosqlbench'
>      ARG: 'tree'
> +  artifacts:
> +    when: always
> +    paths:
> +      - nosqlbench.tree_result.txt
> +      - nosqlbench.tree_t_version.txt
>  
>  perf_cbench:
>    <<: *perf_docker_test_definition
>    variables:
>      <<: *perf_vars_definition
>      BENCH: 'cbench'
> +  artifacts:
> +    when: always
> +    paths:
> +      - cbench-memtx-tree_result.txt
> +      - cbench-memtx-hash_result.txt
> +      - cbench-vinyl-fsync_result.txt
> +      - cbench-vinyl-write_result.txt
> +      - cbench_t_version.txt
>  
>  perf_linkbench_ssd:
>    <<: *perf_docker_test_definition
> @@ -249,6 +287,11 @@ perf_linkbench_ssd:
>    variables:
>      <<: *perf_vars_definition
>      BENCH: 'linkbench'
> +  artifacts:
> +    when: always
> +    paths:
> +      - linkbench.ssd_result.txt
> +      - linkbench.ssd_t_version.txt
>  
>  # Post-testing part
>  
> --
> 1.8.3.1
>  

  parent reply	other threads:[~2020-04-30  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  7:53 Олег Пискунов
2020-04-27 20:23 ` Sergey Bronnikov
2020-04-30  7:32 ` Alexander V. Tikhonov [this message]
2020-05-06  9:08   ` Alexander Turenko
2020-05-06 10:44     ` Oleg Piskunov

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=20200430073226.GA26217@hpalx \
    --to=avtikhon@tarantool.org \
    --cc=o.piskunov@corp.mail.ru \
    --cc=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1] 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