From: "Alexander V. Tikhonov" <avtikhon@tarantool.org> To: Alexander Turenko <alexander.turenko@tarantool.org> Cc: "Alexander V. Tikhonov" <avtikhon@tarantool.org>, tarantool-patches@freelists.org Subject: [tarantool-patches] [PATCH v3 0/2] Implement Gitlab-ci testing process Date: Wed, 19 Jun 2019 09:47:31 +0300 [thread overview] Message-ID: <cover.1560926676.git.avtikhon@tarantool.org> (raw) Implement Gitlab-ci testing process Implemented Gitlba-ci testing process additionaly to travis-ci that is currently uses. New testing process was added to make able to control the high load of the testing processes to avoid of flaky fails on timouts, disks layouts and memory swapping. Also the ability to use needed number of hosts for testing jobs and control jobs per each host, currently jobs set to hosts: sh2 - runs tests which need to be run in line where internal testing suites may run its tests in parallel sh3 - ready to run performance testings sh4 - runs tests OSX and FreeBSD under Virtual Box tool sh5 - runs jobs in parallel: bootstrap jobs which build docker images to speedup testing and build deploy jobs Fixes #4156 Alexander V. Tikhonov (2): Temporary disabled on_shutdown.test.lua test Implement Gitlab-ci testing process .gitlab-ci.yml | 324 +++++++++++++++++++++++++++++++++++++++++++++ .gitlab.mk | 42 ++++++ .travis.mk | 107 +++++++++++---- .travis.yml | 3 + test/box/suite.ini | 2 +- 5 files changed, 450 insertions(+), 28 deletions(-) create mode 100644 .gitlab-ci.yml create mode 100644 .gitlab.mk -- 2.17.1
next reply other threads:[~2019-06-19 6:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-19 6:47 Alexander V. Tikhonov [this message] 2019-06-19 6:47 ` [tarantool-patches] [PATCH v3 1/2] Temporary disabled on_shutdown.test.lua test Alexander V. Tikhonov 2019-06-19 6:47 ` [tarantool-patches] [PATCH v3 2/2] Implement Gitlab-ci testing process Alexander V. Tikhonov
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.1560926676.git.avtikhon@tarantool.org \ --to=avtikhon@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='Re: [tarantool-patches] [PATCH v3 0/2] Implement Gitlab-ci testing process' \ /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