Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>,
	tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v9] gitlab-ci: push Deb/RPM packages to S3 based repos
Date: Mon, 3 Feb 2020 16:45:19 +0300	[thread overview]
Message-ID: <20200203134518.mzt2l4h222rz2w3g@tkn_work_nb> (raw)
In-Reply-To: <5c7b8f38b3d67bd79b129f46be4aeed4d709f15a.1580581971.git.avtikhon@tarantool.org>

> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 3af5a3c8a..8d2a15ce8 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -8,9 +8,24 @@ variables:
>  
>  .release_only_template: &release_only_definition
>    only:
> -    refs:
> -      - master
> -      - /^.*-full-ci$/
> +    - master
> +
> +.fullci_only_template: &fullci_only_definition
> +  only:
> +    - /^.*-full-ci$/
> +
> +.deploy_only_template: &deploy_only_definition
> +  only:
> +    - master
> +  except:
> +    - external_pull_requests
> +    - merge_requests
> +
> +.pack_only_template: &pack_only_definition
> +  only:
> +    - external_pull_requests
> +    - merge_requests
> +    - /^.*-full-ci$/

Schedule jobs still not handled:

https://gitlab.com/help/user/project/pipelines/schedules#using-only-and-except

master / release branches in different repos is not handled too, but
okay, it is not much important, because forking on GitHub do not enable
GitLab CI for the forked repository (unlike Travis-CI).

      parent reply	other threads:[~2020-02-03 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 18:55 Alexander V. Tikhonov
2020-02-03 13:42 ` Alexander Turenko
2020-02-03 14:41   ` Alexander Tikhonov
2020-02-03 13:45 ` Alexander Turenko [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=20200203134518.mzt2l4h222rz2w3g@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v9] gitlab-ci: push Deb/RPM packages to S3 based repos' \
    /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