Fixes tarantool/tarantool-qa#282

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Fixes tarantool/tarantool-qa#281

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Fix the following warning:

NO_WRAP
    Node.js 12 actions are deprecated. For more information see:
    https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
    Please update the following actions to use Node.js 16: actions/checkout
NO_WRAP

Fixes tarantool/tarantool-qa#279

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Fix the following warning:

NO_WRAP
    Node.js 12 actions are deprecated. For more information see:
    https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
    Please update the following actions to use Node.js 16: actions/upload-artifact
NO_WRAP

Fixes tarantool/tarantool-qa#280

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Information about test code coverage is useful on code review.
This patch enables code coverage job in default ci.

NO_CHANGELOG=not a user-visible change
NO_DOC=not a user-visible change
NO_TEST=ci

In PR #7791 the coverage stuff is slightly updated. The changes are
related to excluding some directories where the coverage will not be
calculated. The patch itself is straightforward enough, but I can see
the problems with uploading the results to coveralls.io:

NO_WRAP
    Using lcov file: ./coverage.info
    FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

    <--- Last few GCs --->

    [2683200:0x327c000]    27836 ms: Scavenge 2033.4 (2038.7) -> 2033.2 (2044.2) MB, 6.8 / 0.0 ms  (average mu = 0.258, current mu = 0.243) allocation failure
    [2683200:0x327c000]    27854 ms: Scavenge 2036.7 (2044.2) -> 2037.1 (2044.4) MB, 15.6 / 0.0 ms  (average mu = 0.258, current mu = 0.243) allocation failure
    [2683200:0x327c000]    27871 ms: Scavenge 2037.2 (2044.4) -> 2036.7 (2055.9) MB, 17.1 / 0.0 ms  (average mu = 0.258, current mu = 0.243) allocation failure

    <--- JS stacktrace --->

    ==== JS stack trace =========================================

        0: ExitFrame [pc: 0x140dc19]
    Security context: 0x2481918808d1 <JSObject>
        1: encode(aka encode) [0x23ec5e514a11] [/opt/actions-runner/_work/_actions/coverallsapp/github-action/v1.1.2/node_modules/qs/lib/utils.js:~118] [pc=0x193ecd3d5d82](this=0x35d34e4804b1 <undefined>,0x1e5895380119 <Very long string[60387428]>)
        2: stringify(aka stringify) [0x23ec5e5174c9] [/opt/actions-runner/_work/_actions/coverallsapp/github-action/v1.1.2/n...

     1: 0xa1a640 node::Abort() [/opt/actions-runner/externals/node12/bin/node]
     2: 0xa1aa4c node::OnFatalError(char const*, char const*) [/opt/actions-runner/externals/node12/bin/node]
     3: 0xb9a62e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/opt/actions-runner/externals/node12/bin/node]
     4: 0xb9a9a9 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/opt/actions-runner/externals/node12/bin/node]
     5: 0xd57c25  [/opt/actions-runner/externals/node12/bin/node]
     6: 0xd582b6 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/opt/actions-runner/externals/node12/bin/node]
     7: 0xd64b75 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/opt/actions-runner/externals/node12/bin/node]
     8: 0xd65a25 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/opt/actions-runner/externals/node12/bin/node]
     9: 0xd670cf v8::internal::Heap::HandleGCRequest() [/opt/actions-runner/externals/node12/bin/node]
    10: 0xd15b35 v8::internal::StackGuard::HandleInterrupts() [/opt/actions-runner/externals/node12/bin/node]
    11: 0x1071176 v8::internal::Runtime_StackGuard(int, unsigned long*, v8::internal::Isolate*) [/opt/actions-runner/externals/node12/bin/node]
    12: 0x140dc19  [/opt/actions-runner/externals/node12/bin/node]
NO_WRAP

I have tried to use the latest version of the action (1.1.3), but I have
got the same issue.

It looks like it is a `coverallsapp/github-action` issue due to issue
in JavaScript due to inefficient amount of memory. The corresponding
bug [1] was filed against the repo.

So I suggest switching to the console utility `coveralls-lcov`. I did
some internal testing and it works fine.

[1] https://github.com/coverallsapp/github-action/issues/133

Fixes tarantool/tarantool-qa#278

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

It's quite inconvenient to extend LuaJIT integration workflow now: one
needs to patch GitHub workflow file in Tarantool repository and then
setup integration testing in LuaJIT repository.

This patch introduces a new workflow parameter that can replace several
existing parameters (e.g. buildtype and GC64) and allow to easy extend
integration CI in LuaJIT (with rare little touches in Tarantool).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Reviewed-by: Sergey Kaplun <skaplun@tarantool.org>
Reviewed-by: Yaroslav Lobankov <y.lobankov@tarantool.org>
Signed-off-by: Igor Munkin <imun@tarantool.org>

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Usually, GitHub actions are named like `foo-bar` rather than `foo_bar`.
A few widely known examples: upload-artifact [1], download-artifact [2],
setup-python [3], setup-node [4]. So let's stick to this approach also.

[1] https://github.com/actions/upload-artifact
[2] https://github.com/actions/download-artifact
[3] https://github.com/actions/setup-python
[4] https://github.com/actions/setup-node

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Add the redos_7.3.yml workflow to build Tarantool packages (x86_64) for
the RedOS 7.3 system.

Packages are created by https://github.com/packpack/packpack.

NO_DOC=ci
NO_TEST=ci

`make api` generates `src/module.h`. `make module_api` is the target for
compiling a library for testing of the module API:
`test/app-tap/module_api.so`. It depends on the `api` target.

Both works for generating `module.h`, but `make api` don't do extra
unneeded actions.

NO_DOC=Not a user visible change.
NO_TEST=It is CI workflow. It would be too strong to test each part of
        the testing/deployment infrastructure.
NO_CHANGELOG=Not a user visible change.

The `ubuntu-18.04` environment is deprecated, so let's switch to
`ubuntu-latest` where it is safe. For more details see [1].

[1] https://github.com/actions/virtual-environments/issues/6002

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

See d3f32d18 for explanation.

NO_CHANGELOG=ci
NO_DOC=ci
NO_TEST=ci

Publishing workflow will run building module API documentation for
opened or reopened pull request with label "full-ci" and will publish
documentation on Github Pages on push to the master branch.

NO_CHANGELOG=ci
NO_DOC=ci
NO_TEST=ci

Report workflow failures in PRs made by TarantoolBot to the same chat
as with stable branches. Such PRs are used for automated integration
testing, so it's important for the team to notice failures in them.
There is no personal chat for TarantoolBot and no need to make one.

NO_DOC=CI reporting
NO_TEST=CI reporting
NO_CHANGELOG=CI reporting

This patch allows to call `report-job-status` action with only one
input: `bot-token`. VK Teams chat ID has the default value in current
action, API URL has the default value in [1].

[1] `tarantool/actions/report-job-status`

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

This patch adds a warning about using the action in pull requests
created from forks. GitHub secrets are not passed to workflows in
this case [1] and due to this limitation the action will not work
correctly for such pull requests.

[1] https://docs.github.com/en/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

This patch adds a temporary workaround for LuaJIT profiling tests to
avoid runners shutdown due to no space left on the disk. The profiling
tests may produce profiles until fully fill up the runner [1].

The workaround is based on implementing disk quotas.

In two words, it creates a 1GB file (disk image), formats this file as
an ext4 filesystem, mounts this filesystem to some mount pont and sets
`LUAJIT_TEST_VARDIR=<mount point>`. In this case LuaJIT tests will use
this dir for storing various test data/profiles and not be able to fill
up the runner.

[1] https://github.com/tarantool/tarantool/issues/7472

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

This patch introduces the new `report-job-status` action that is used
for sending notifications to the VK Teams messenger on the job failure.
It replaces the old `send-telegram-notify` action sending similar text
notifications to the Telegram messenger.

The new action selects the corresponding chat for the notification on
failure and uses the `tarantool/actions/report-job-status` action [1]
for sending it to:

* the team chat (Tarantool CI/CD reports) - if the job started on any
  event in the master or release branch (1.10, 2.10, etc);

* a personal chat (created by the committer) – if the job started on
  creating/updating a pull request or any event in other branches.

[1] https://github.com/tarantool/actions/tree/master/report-job-status

Resolves tarantool/tarantool-qa#258

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

- Fix checkout with submodules
- Fix publish action version

NO_CHANGELOG=ci
NO_DOC=ci
NO_TEST=ci

NO_DOC=internal
NO_TEST=internal

This patch fixes the following issue: the submodule_update.yml workflow
always updated the tarantool submodule in the tarantool-ee repo to the
last commit from the `master` branch, even if it was tarantool-ee 2.10.
Now it is fixed.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

GitHub shuts down the macos-10.15 virtual environments [1] and
the bug [2] is fixed. So it's time to move the OSX static build
testing to a newer environment.

[1] https://github.com/actions/virtual-environments/issues/5583
[2] https://github.com/tarantool/tarantool/issues/7459

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

- Run the workflow in tarantool/tarantool repo only
- Fix the condition to compose PR title prefix
- Add a small description for created PRs

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Bump tarantool submodule in tarantool-ee via pull requests:

* tarantool@master -> tarantool-ee@TarantoolBot/update-tarantool-master
* tarantool@2.10 -> tarantool-ee@TarantoolBot/update-tarantool-2.10

If there is an open PR already, it will be updated every time when
a new commit is pushed to tarantool@master or tarantool@2.10.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Closes tarantool/tarantool-ee#175

This patch adds missing `ninja` package to deps for FreeBSD and OSX
systems to provide possibility to use `ninja` as a build system on
them.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

If Tarantool tests fail in LuaJIT integration workflow used in
tarantool/luajit repository and LuaJIT submodule is already bumped in
tarantool/tarantool repository, one can't rerun the failed job since
"LuaJIT bump" step brings down the whole pipeline with "nothing to
commit" reason.

There are still many flaky tests, so to make this integration workflow
rerunnable from tarantool/luajit repository --allow-empty option is
added to the git commit command.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Reviewed-by: Yaroslav Lobankov <y.lobankov@tarantool.org>
Reviewed-by: Sergey Kaplun <skaplun@tarantool.org>
Signed-off-by: Igor Munkin <imun@tarantool.org>

Ubuntu Impish Indri (21.10) has reached end of life
(https://wiki.ubuntu.com/Releases). There will be
no further releases of Tarantool for Ubuntu 21.10,
hence there's no need to run tests and check
packaging.

NO_TEST=ci
NO_DOC=ci

Resolves tarantool/tarantool-qa#257

The 2.8 branch is not longer supported. So there is no sense to keep
the logic for it.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Now it's time to drop the `.gitlab.mk` makefile because `.pack.mk` has
fully replaced it.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

In order to support parallel cmake build in the `test-jepsen` target
we need to run Jepsen testing in a `debian-buster` container instead
of `debian-stretch` due to the old `cmake` version in it. The `cmake`
utility started to support `--parallel` option since 3.12 version [1].

In Debian Stretch `cmake` has version 3.7.
In Debian Buster `cmake` has version 3.13.

[1] https://cmake.org/cmake/help/latest/release/3.12.html#command-line

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

A note for the `.gitlab.mk` makefile:

Mentions about `.travis.mk` in `.gitlab.mk` file will be removed in
the scope of refactoring it later.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

A note for arm64 OSX workflows:

The `arch -arm64` command prior to calling the makefile was omitted
because now the GitHub Actions agent has a build for arm64 machines.
Hence the agent is able to run without Rosetta 2 binary translator.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

This patch adds actions with installing deps for Debian, FreeBSD, and
OSX operation systems. Also, it adds an action with installing deps for
Jepsen testing. Debian, FreeBSD, and OSX actions should be used before
running tests on the corresponding operation systems. Jepsen action
should be used before running Jepsen tests.

Reasoning:

1. The makefile w/o targets with deps installation is OS-independent.
   It should work on all systems.

2. Deps installation is more about env preparation rather than building
   and testing. Moreover, it is OS-dependent. So it's logical to take it
   outside the makefile into a GitHub action.

3. If we need testing on other operation systems, for example, CentOS,
   we will just create a special action with deps installation for that.
   No changes for the makefile will be needed. All should work out of
   the box.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Disable tests while building packages in the reusable_build.yml workflow
to speed up the build process in integration testing for tarantool and
modules/connectors.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

This patch introduces reusable workflow used by integration testing
machinery run within tarantool/luajit repository.

For the first attempt GitHub action has been used, but its fetch (or
more precisely unpack) phase fails due to test/test-run.py symlink into
test-run submodule (the action being used doesn't fetch it while packing
tarantool repository). As the alternative for removing this symlink, it
was decided to use reusable workflows despite its known limitations
(e.g. inability to use the testing matrix) until the issue with symlink
is resolved in any possible way.

As an alternate way, a common action to be used in all submodules for
integration testing can be added to tarantool/actions repository.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Reviewed-by: Yaroslav Lobankov <y.lobankov@tarantool.org>
Reviewed-by: Sergey Bronnikov <sergeyb@tarantool.org>
Signed-off-by: Igor Munkin <imun@tarantool.org>

Added 'tarantool/actions/cleanup' action to each job which uses
self-hosted runners.

The action cleans workspace directory of self-hosted runner after
previous run. The main reason to add this action is 'Need a single
revision' error [1] caused by a conflict of submodule versions,
the standard 'actions/checkout' action fails with this error. It's a
well-known problem and related issue [2] is still opened.

[1] https://github.com/tarantool/tarantool-qa/issues/145
[2] https://github.com/actions/checkout/issues/418

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Closes tarantool/tarantool-qa#145

To ensure that regular and GC64 jobs in packaging workflows don't
overwrite artifacts of each other, we need to use a different artifact
name per job.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

In PR #7090 we forgot to update the path to gather failure artifacts for
many packaging workflows. Now it is fixed.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci