Skip to content
Snippets Groups Projects
Commit eb891308 authored by Yaroslav Lobankov's avatar Yaroslav Lobankov Committed by Kirill Yukhin
Browse files

ci: remove builds of Fedora EOL releases 

- Fedora 30
- Fedora 31
- Fedora 32
- Fedora 33

See for details: https://docs.fedoraproject.org/en-US/releases/eol

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
parent 4eaff4e0
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
.github/workflows/fedora_30.yml deleted 100644 → 0
+ 0
− 74
View file @ 4eaff4e0
name: fedora_30
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:
fedora_30:
# 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: 'fedora'
DIST: '30'
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: fedora-30
retention-days: 21
path: build/usr/src/*/tarantool-*/test/var/artifacts
.github/workflows/fedora_31.yml deleted 100644 → 0
+ 0
− 74
View file @ 4eaff4e0
name: fedora_31
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:
fedora_31:
# 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: 'fedora'
DIST: '31'
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: fedora-31
retention-days: 21
path: build/usr/src/*/tarantool-*/test/var/artifacts
.github/workflows/fedora_32.yml deleted 100644 → 0
+ 0
− 74
View file @ 4eaff4e0
name: fedora_32
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:
fedora_32:
# 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: 'fedora'
DIST: '32'
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: fedora-32
retention-days: 21
path: build/usr/src/*/tarantool-*/test/var/artifacts
.github/workflows/fedora_33.yml deleted 100644 → 0
+ 0
− 74
View file @ 4eaff4e0
name: fedora_33
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:
fedora_33:
# 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: 'fedora'
DIST: '33'
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: fedora-33
retention-days: 21
path: build/usr/src/*/tarantool-*/test/var/artifacts
.github/workflows/fedora_33_aarch64.yml deleted 100644 → 0
+ 0
− 68
View file @ 4eaff4e0
name: fedora_33_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:
fedora_33_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: 'fedora'
DIST: '33'
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: fedora-33
retention-days: 21
path: build/usr/src/*/tarantool-*/test/var/artifacts
changelogs/unreleased/drop-fedora-30-31-32-33-ci-cd.md 0 → 100644
+ 3
− 0
View file @ eb891308
## feature/build
* Stop support of Fedora 30/31/32/33 builds.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment