- CI: serialization bug fix - reverted concurrency lock to workflow level instead of job level which was causing issues due to incorrect cache at expected jobs

This commit is contained in:
=
2025-02-26 20:00:05 +05:30
parent 950cb7f5b0
commit 05ccccded8

View File

@@ -46,11 +46,16 @@ on:
jobs: jobs:
common: common:
name: Shared Steps name: Wait for other jobs
# since build cache, test-build cache, test-run cache are involved, out of order exec if serialization is on individual jobs will wreak all sorts of havoc
# so we serialize on the entire workflow
concurrency:
group: serialize-workflow
strategy: strategy:
fail-fast: false fail-fast: false
runs-on: 'macos-15' runs-on: 'macos-15'
steps: steps:
- run: echo "No other contending jobs are running now..."
- name: Set short commit hash - name: Set short commit hash
id: commit-id id: commit-id
run: | run: |
@@ -64,8 +69,6 @@ jobs:
build: build:
name: Build SideStore - ${{ inputs.release_tag }} name: Build SideStore - ${{ inputs.release_tag }}
needs: common needs: common
concurrency:
group: build-number-increment # serialize for build num cache access
strategy: strategy:
fail-fast: false fail-fast: false
matrix: matrix:
@@ -80,8 +83,6 @@ jobs:
release-channel: ${{ steps.release-channel.outputs.RELEASE_CHANNEL }} release-channel: ${{ steps.release-channel.outputs.RELEASE_CHANNEL }}
steps: steps:
- run: echo "No other contending jobs are running now...Build is ready to start"
- name: Set beta status - name: Set beta status
run: echo "IS_BETA=${{ inputs.is_beta }}" >> $GITHUB_ENV run: echo "IS_BETA=${{ inputs.is_beta }}" >> $GITHUB_ENV