From abd9bbf0be95c97eb8eaeae6ad7dcf975e009af5 Mon Sep 17 00:00:00 2001
From: artembo <artembo@me.com>
Date: Fri, 13 May 2022 18:37:35 +0300
Subject: [PATCH] ci: add Ubuntu Jammy (22.04) workflow
Add the ubuntu_22_04.yml and ubuntu_22_04_aarch64.yml workflow files to
build Tarantool packages for x86_64 and aarch64 systems.
Closes tarantool/tarantool-qa#237
NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
Co-authored-by: Yaroslav Lobankov <y.lobankov@tarantool.org>
---
.github/workflows/ubuntu_22_04.yml | 74 ++++++++++++++++++++++
.github/workflows/ubuntu_22_04_aarch64.yml | 68 ++++++++++++++++++++
2 files changed, 142 insertions(+)
create mode 100644 .github/workflows/ubuntu_22_04.yml
create mode 100644 .github/workflows/ubuntu_22_04_aarch64.yml
diff --git a/.github/workflows/ubuntu_22_04.yml b/.github/workflows/ubuntu_22_04.yml
new file mode 100644
index 0000000000..9bc30a5da4
--- /dev/null
+++ b/.github/workflows/ubuntu_22_04.yml
@@ -0,0 +1,74 @@
+name: ubuntu_22_04
+
+on:
+ push:
+ branches:
+ - 'master'
+ - '[0-9].[0-9]+'
+ tags:
+ - '**'
+ pull_request:
+ types: [opened, reopened, synchronize, labeled]
+ workflow_dispatch:
+
+concurrency:
+ # Update of a developer branch cancels the previously scheduled workflow
+ # run for this branch. However, the 'master' branch, release branch (1.10,
+ # 2.8, etc.), and tag workflow runs are never canceled.
+ #
+ # We use a trick here: define the concurrency group as 'workflow run ID' +
+ # 'workflow run attempt' because it is a unique combination for any run.
+ # So it effectively discards grouping.
+ #
+ # Important: we cannot use `github.sha` as a unique identifier because
+ # pushing a tag may cancel a run that works on a branch push event.
+ group: ${{ (
+ github.ref == 'refs/heads/master' ||
+ github.ref == 'refs/heads/1.10' ||
+ startsWith(github.ref, 'refs/heads/2.') ||
+ startsWith(github.ref, 'refs/tags/')) &&
+ format('{0}-{1}', github.run_id, github.run_attempt) ||
+ format('{0}-{1}', github.workflow, github.ref) }}
+ cancel-in-progress: true
+
+jobs:
+ ubuntu_22_04:
+ # Run on push to the 'master' and release branches of tarantool/tarantool
+ # or on pull request if the 'full-ci' label is set.
+ if: github.repository == 'tarantool/tarantool' &&
+ ( github.event_name != 'pull_request' ||
+ contains(github.event.pull_request.labels.*.name, 'full-ci') )
+
+ runs-on: ubuntu-20.04-self-hosted
+
+ strategy:
+ fail-fast: false
+ matrix:
+ build-type: [ '', 'gc64' ]
+
+ steps:
+ - uses: actions/checkout@v2.3.4
+ with:
+ fetch-depth: 0
+ submodules: recursive
+ - uses: ./.github/actions/environment
+ - name: packaging
+ env:
+ RWS_AUTH: ${{ secrets.RWS_AUTH }}
+ OS: 'ubuntu'
+ DIST: 'jammy'
+ GC64: ${{ matrix.build-type == 'gc64' }}
+ uses: ./.github/actions/pack_and_deploy
+ - name: call action to send Telegram message on failure
+ env:
+ TELEGRAM_TOKEN: ${{ secrets.TELEGRAM_CORE_TOKEN }}
+ TELEGRAM_TO: ${{ secrets.TELEGRAM_CORE_TO }}
+ uses: ./.github/actions/send-telegram-notify
+ if: failure()
+ - name: artifacts
+ uses: actions/upload-artifact@v2
+ if: failure()
+ with:
+ name: ubuntu-jammy
+ retention-days: 21
+ path: ${{ env.VARDIR }}/artifacts
diff --git a/.github/workflows/ubuntu_22_04_aarch64.yml b/.github/workflows/ubuntu_22_04_aarch64.yml
new file mode 100644
index 0000000000..24e16b6f51
--- /dev/null
+++ b/.github/workflows/ubuntu_22_04_aarch64.yml
@@ -0,0 +1,68 @@
+name: ubuntu_22_04_aarch64
+
+on:
+ push:
+ branches:
+ - 'master'
+ - '[0-9].[0-9]+'
+ tags:
+ - '**'
+ pull_request:
+ types: [opened, reopened, synchronize, labeled]
+ workflow_dispatch:
+
+concurrency:
+ # Update of a developer branch cancels the previously scheduled workflow
+ # run for this branch. However, the 'master' branch, release branch (1.10,
+ # 2.8, etc.), and tag workflow runs are never canceled.
+ #
+ # We use a trick here: define the concurrency group as 'workflow run ID' +
+ # 'workflow run attempt' because it is a unique combination for any run.
+ # So it effectively discards grouping.
+ #
+ # Important: we cannot use `github.sha` as a unique identifier because
+ # pushing a tag may cancel a run that works on a branch push event.
+ group: ${{ (
+ github.ref == 'refs/heads/master' ||
+ github.ref == 'refs/heads/1.10' ||
+ startsWith(github.ref, 'refs/heads/2.') ||
+ startsWith(github.ref, 'refs/tags/')) &&
+ format('{0}-{1}', github.run_id, github.run_attempt) ||
+ format('{0}-{1}', github.workflow, github.ref) }}
+ cancel-in-progress: true
+
+jobs:
+ ubuntu_22_04_aarch64:
+ # Run on push to the 'master' and release branches of tarantool/tarantool
+ # or on pull request if the 'full-ci' label is set.
+ if: github.repository == 'tarantool/tarantool' &&
+ ( github.event_name != 'pull_request' ||
+ contains(github.event.pull_request.labels.*.name, 'full-ci') )
+
+ runs-on: graviton
+
+ steps:
+ - uses: actions/checkout@v2.3.4
+ with:
+ fetch-depth: 0
+ submodules: recursive
+ - uses: ./.github/actions/environment
+ - name: packaging
+ env:
+ RWS_AUTH: ${{ secrets.RWS_AUTH }}
+ OS: 'ubuntu'
+ DIST: 'jammy'
+ uses: ./.github/actions/pack_and_deploy
+ - name: call action to send Telegram message on failure
+ env:
+ TELEGRAM_TOKEN: ${{ secrets.TELEGRAM_CORE_TOKEN }}
+ TELEGRAM_TO: ${{ secrets.TELEGRAM_CORE_TO }}
+ uses: ./.github/actions/send-telegram-notify
+ if: failure()
+ - name: artifacts
+ uses: actions/upload-artifact@v2
+ if: failure()
+ with:
+ name: ubuntu-jammy
+ retention-days: 21
+ path: ${{ env.VARDIR }}/artifacts
--
GitLab