From: "Oleg Piskunov" <o.piskunov@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 v1] gitlab-ci: integration testing vshard Date: Mon, 18 May 2020 15:46:13 +0300 [thread overview] Message-ID: <1589805973.787545255@f462.i.mail.ru> (raw) In-Reply-To: <20200517123112.GA17304@hpalx> [-- Attachment #1: Type: text/plain, Size: 1149 bytes --] Sasha, thanks for review. Below my comments. >> +test_module_vshard: >> + cmake . -DCMAKE_BUILD_TYPE=RelWithDebInfo -DENABLE_WERROR=ON -DENABLE_DIST=ON ${CMAKE_EXTRA_PARAMS} >> + make -j > >Here is the Tarantool building and there is already special rule exists >for it, let's use it, like: > >test_module_vshard: build_debian The reason is that tarantoolctl needed for testing vshard module. I’ll reuse «build_debian», but will add -DENABLE_DIST=ON option to it for enable tarantoolctl during «make install». >> + make install >> + git clone https://github.com/tarantool/vshard.git tarantool/vshard > >A little bit confising here, if you want additional directory like >'tarantool' may be it's better to change it to some name like 'module'. Sure, will change path to just «vshard» >> + cd tarantool/vshard && git submodule update --init --recursive \ >> + && cmake . && make test > >Seems extra 'submodule update' call to git can be merged to its 'clone' >call, like: > >git clone --recurse-submodules https://... Sure. Will do. -- Oleg Piskunov [-- Attachment #2: Type: text/html, Size: 1989 bytes --]
next prev parent reply other threads:[~2020-05-18 12:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-17 7:35 Oleg Piskunov 2020-05-17 12:31 ` Alexander V. Tikhonov 2020-05-18 12:46 ` Oleg Piskunov [this message] 2020-05-18 9:00 ` Sergey Bronnikov 2020-05-18 13:05 ` 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=1589805973.787545255@f462.i.mail.ru \ --to=o.piskunov@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=avtikhon@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1] gitlab-ci: integration testing vshard' \ /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