From: "Oleg Piskunov" <o.piskunov@tarantool.org> To: "Alexander Turenko" <alexander.turenko@tarantool.org> Cc: tarantool-patches@dev.tarantool.org, "Олег Пискунов" <o.piskunov@corp.mail.ru> Subject: Re: [Tarantool-patches] [PATCH v1] Keep perf results as gitlab-ci artifacts Date: Wed, 06 May 2020 13:44:00 +0300 [thread overview] Message-ID: <1588761840.98541774@f114.i.mail.ru> (raw) In-Reply-To: <20200506090802.x3dro6djzqir37cy@tkn_work_nb> [-- Attachment #1: Type: text/plain, Size: 1733 bytes --] Alexander, thanks a lot for review! >Среда, 6 мая 2020, 12:08 +03:00 от Alexander Turenko <alexander.turenko@tarantool.org>: > >> Keep perf results as gitlab-ci artifacts > >Nit: Let's add some prefix: I would use 'gitlab-ci'. Using of prefixes >is convenient and allows to traverse over commits faster. ok. >> >> Gitlab-ci pipeline modified in order to keep performance results into gitlab-ci artifacts. > >Nit: Keep commit message body lines within 72 symbols. ok. >> >> Closes #4920 >> >> Github: https://github.com/tarantool/tarantool/tree/opiskunov/gh-4920-perf-artifacts >> Issue: https://github.com/tarantool/tarantool/issues/4920 > >Nit: Don't include issue no / branch into a commit message, only within >a email. Place them under '---' to distinguish from a commit message >itself. ok >> --- >> .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 > >I would deploy a directory with result as an artefact or use globs >(GitLab CI supports both). gitlab-ci.yml should not lean on hardcoded >bench-run paths. Can we formalize bench-run contract for performance >measurement results? Maybe, `${benchmark}_results` directory? Or >`${benchmark}_${conf}_results` if names intersection may be troublesome. I will use wildcards for this. -- Oleg Piskunov [-- Attachment #2: Type: text/html, Size: 3222 bytes --]
prev parent reply other threads:[~2020-05-06 10:44 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 2020-05-06 9:08 ` Alexander Turenko 2020-05-06 10:44 ` Oleg Piskunov [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=1588761840.98541774@f114.i.mail.ru \ --to=o.piskunov@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=o.piskunov@corp.mail.ru \ --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