Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>,
	Maxim Kokryashkin <m.kokryashkin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 0/2] More enhancements in LuaJIT CI
Date: Wed, 18 Jan 2023 12:24:01 +0300	[thread overview]
Message-ID: <Y8e6sR2/qsEKRqGr@tarantool.org> (raw)
In-Reply-To: <cover.1673534407.git.imun@tarantool.org>

I've checked the patches into all long-term branches in tarantool/luajit
and bumped a new version in master, 2.10 and 1.10.

On 12.01.23, Igor Munkin wrote:
> This series consists of the two patches caused by recent runner renaming
> activity.
> 
> The first one changes the way workflow is dispatched to the proper
> runner (see the details in the corresponding commit message).
> 
> The second one caused by fluke: due to runner renaming we can't proceed
> to use the previous approach to pass the machine name to LuaJIT
> integration workflow. Hence, we ought to implement something similar
> made in scope of the first patch. Occasionally, I've found that GitHub
> team finally implemented strategy matrix for reusable workflows, so I
> simply made a carbon copy of the <test-luajit> job configuration for
> Tarantool integration testing. As a result the integration workflow is
> also adjusted for the new runner dispatching strategy in scope of
> #8145[1].
> 
> Branch: https://github.com/tarantool/luajit/tree/imun/fix-runner-names
> CI is green: https://github.com/tarantool/luajit/commit/43adedc
> 
> [1]: https://github.com/tarantool/tarantool/pull/8145
> 
> Igor Munkin (2):
>   ci: change runner dispatch for LuaJIT testing
>   ci: use strategy matrix for integration workflow
> 
>  .github/workflows/gnumake-builds-testing.yml |  20 +-
>  .github/workflows/lint.yml                   |   2 +-
>  .github/workflows/testing.yml                | 210 +++----------------
>  3 files changed, 35 insertions(+), 197 deletions(-)
> 
> -- 
> 2.34.0
> 

-- 
Best regards,
IM

      parent reply	other threads:[~2023-01-18  9:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 14:51 Igor Munkin via Tarantool-patches
2023-01-12 14:51 ` [Tarantool-patches] [PATCH luajit 1/2] ci: change runner dispatch for LuaJIT testing Igor Munkin via Tarantool-patches
2023-01-12 23:23   ` Maxim Kokryashkin via Tarantool-patches
2023-01-13  7:10     ` Sergey Kaplun via Tarantool-patches
2023-01-16  7:55       ` Igor Munkin via Tarantool-patches
2023-01-16 12:34         ` Maxim Kokryashkin via Tarantool-patches
2023-01-16  7:53     ` Igor Munkin via Tarantool-patches
2023-01-12 14:51 ` [Tarantool-patches] [PATCH luajit 2/2] ci: use strategy matrix for integration workflow Igor Munkin via Tarantool-patches
2023-01-12 23:27   ` Maxim Kokryashkin via Tarantool-patches
2023-01-13  7:16     ` Sergey Kaplun via Tarantool-patches
2023-01-16  8:00       ` Igor Munkin via Tarantool-patches
2023-01-16 12:35         ` Maxim Kokryashkin via Tarantool-patches
2023-01-16  7:58     ` Igor Munkin via Tarantool-patches
2023-01-18  9:24 ` Igor Munkin via Tarantool-patches [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=Y8e6sR2/qsEKRqGr@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imun@tarantool.org \
    --cc=m.kokryashkin@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit 0/2] More enhancements in LuaJIT CI' \
    /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