Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1] Set full testing for all branches
Date: Wed, 3 Jun 2020 15:29:32 +0300	[thread overview]
Message-ID: <20200603122932.qxwmu65xmkvcovcv@tkn_work_nb> (raw)
In-Reply-To: <20200602175642.GA4599@hpalx>

I have no more objections.

If everything works as expected and we're ready to such amount of jobs,
the change will allow to catch some problems before a patch will land
into master.

BTW, please add 'gitlab-ci' prefix.

> > >  .pack_only_template: &pack_only_definition
> > >    only:
> > >      - schedules
> > >      - external_pull_requests
> > >      - merge_requests
> > > -    - /^.*-full-ci$/
> > > +    - branches
> > > +    - tags
> > 
> > First, there is not reason to list 'schedules', 'external_pull_requests'
> > and so if you want to just run it everywhere.
> > 
> 
> Actually I just wanted to make it more visible for the users, but anyway
> if it not really needed I'll change it to "except: master".
> 
> > Second, we should not run both 'just packaging' and 'packaging and
> > deployment' jobs on master. I would make ''pack_only_template' be just
> > 'except: master'. Yep, it is not perfect: 'schedules',
> > 'external_pull_requests' will don't run neither 'pack', nor 'deploy'.
> > But this change is simple and downsides are acceptable.
> > 
> 
> Right, it is the same as previous my comment.

I would mention the known downside somewhere, preferably just in this
config.

  reply	other threads:[~2020-06-03 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 18:35 Alexander V. Tikhonov
2020-05-21 19:42 ` Sergey Bronnikov
2020-05-22 12:05   ` Oleg Piskunov
2020-06-01 12:39 ` Alexander Turenko
2020-06-02 17:56   ` Alexander V. Tikhonov
2020-06-03 12:29     ` Alexander Turenko [this message]
2020-06-11 11:35 ` 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=20200603122932.qxwmu65xmkvcovcv@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1] Set full testing for all branches' \
    /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