From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v1] gitlab-ci: merge test and deploy stages
Date: Sat, 6 Jul 2019 14:59:00 +0300 [thread overview]
Message-ID: <20190706115900.ek5nfsy4m7amfjxj@tkn_work_nb> (raw)
In-Reply-To: <63679f3053e9a776f15ff64bad19ddba2d91b5e1.1562328624.git.avtikhon@tarantool.org>
Pushed to master, 2.1 and 1.10.
WBR, Alexander Turenko.
On Fri, Jul 05, 2019 at 03:12:25PM +0300, Alexander V. Tikhonov wrote:
> Current results have some tests with flaky results, which
> blocks the deploy stage - decided to merge deploy stage into
> test stage temporary to fix it.
>
> Part of #4156
>
> ---
>
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-4156-gitlab-ci-testing
> Issue: https://github.com/tarantool/tarantool/issues/4156
>
> .gitlab-ci.yml | 27 +++++++++++++--------------
> 1 file changed, 13 insertions(+), 14 deletions(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 9d374cd61..818a84fe0 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -1,6 +1,5 @@
> stages:
> - test
> - - deploy
>
> variables:
> IMAGE_TEST: "${CI_REGISTRY}/${CI_PROJECT_PATH}/testing/debian-stretch:latest"
> @@ -143,7 +142,7 @@ centos_6:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -157,7 +156,7 @@ centos_7:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy_test
> variables:
> @@ -171,7 +170,7 @@ fedora_28:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy_test
> variables:
> @@ -185,7 +184,7 @@ fedora_29:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy_test
> variables:
> @@ -199,7 +198,7 @@ fedora_30:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy_test
> variables:
> @@ -213,7 +212,7 @@ ubuntu_14_04:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -227,7 +226,7 @@ ubuntu_16_04:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -241,7 +240,7 @@ ubuntu_18_04:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -255,7 +254,7 @@ ubuntu_18_10:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -269,7 +268,7 @@ ubuntu_19_04:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -283,7 +282,7 @@ debian_8:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -297,7 +296,7 @@ debian_9:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> @@ -311,7 +310,7 @@ debian_10:
> refs:
> - master
> - /^.*-full-ci$/
> - stage: deploy
> + stage: test
> tags:
> - deploy
> variables:
> --
> 2.17.1
>
parent reply other threads:[~2019-07-06 11:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <63679f3053e9a776f15ff64bad19ddba2d91b5e1.1562328624.git.avtikhon@tarantool.org>]
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=20190706115900.ek5nfsy4m7amfjxj@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v1] gitlab-ci: merge test and deploy stages' \
/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