From: "Alexander V. Tikhonov" <avtikhon@tarantool.org> To: Oleg Piskunov <o.piskunov@tarantool.org>, Sergey Bronnikov <sergeyb@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH v1 0/2] set to gitlab-ci static build with Dockerfile Date: Tue, 7 Apr 2020 17:03:24 +0300 [thread overview] Message-ID: <cover.1586263386.git.avtikhon@tarantool.org> (raw) gitlab-ci: set static docker build release testing Found that static build based on Dockerfile used external link and missed that it was removed, like it was in #4830. To avoid of the same issues the cache for building the Dockerfile was disabled with '--no-cache' option at docker build command. Returned the static build based on Dockerfile to gitlab-ci release branches testing after the issues with missed openssl version fixed at PR #4831. Follow up #4831 Follow up #4830 Github: https://github.com/tarantool/tarantool/tree/avtikhon/dockerfile-static-build-full-ci Issue: https://github.com/tarantool/tarantool/issues/4830 Issue: https://github.com/tarantool/tarantool/issues/4831 Alexander V. Tikhonov (2): build: disable cache for static build Dockerfile gitlab-ci: set static docker build release testing .gitlab-ci.yml | 4 +++- .travis.mk | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) -- 2.17.1
next reply other threads:[~2020-04-07 14:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-07 14:03 Alexander V. Tikhonov [this message] 2020-04-07 14:03 ` [Tarantool-patches] [PATCH v1 1/2] build: disable cache for static build Dockerfile Alexander V. Tikhonov 2020-04-14 8:28 ` Sergey Bronnikov 2020-04-15 8:42 ` Oleg Piskunov 2020-04-07 14:03 ` [Tarantool-patches] [PATCH v1 2/2] gitlab-ci: set static docker build release testing Alexander V. Tikhonov 2020-04-14 8:28 ` Sergey Bronnikov 2020-04-15 8:44 ` Oleg Piskunov 2020-04-15 12:48 ` [Tarantool-patches] [PATCH v1 0/2] set to gitlab-ci static build with Dockerfile 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=cover.1586263386.git.avtikhon@tarantool.org \ --to=avtikhon@tarantool.org \ --cc=o.piskunov@tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1 0/2] set to gitlab-ci static build with Dockerfile' \ /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