Skip to content

Apply concurrency control to swift-package-test, cancelling previously running workflows of the same kind #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Apply concurrency control to swift-package-test, cancelling previously running workflows of the same kind #111

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/swift_package_test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,11 @@ on:
description: "Boolean to enable providing the GITHUB_TOKEN to downstream job."
default: false

## We are cancelling previously triggered workflow runs
concurrency:
group: ${{ github.workflow }}-${{ github.job }}-${{ github.ref }}-package-test
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I could tell which PR it was and whether it was the linux-build or windows-build job inside swift_package_test, there was no way — using only the information available within swift_package_test — to determine whether it was triggered from tests_with_docker or tests_without_docker in the parent workflow.

cancel-in-progress: true

jobs:
linux-build:
name: Linux (${{ matrix.swift_version }} - ${{ matrix.os_version }})
Expand Down