#53080 closed defect (bug) (fixed)
Use the `concurrency` option in GitHub Actions workflows.
Reported by: | desrosj | Owned by: | desrosj |
---|---|---|---|
Milestone: | 5.8 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
GitHub has recently announced a new concurrency
key for use at the workflow and job level to ensure only a single workflow run or job is in progress. When used in combination with the cancel-in-progress
key, incomplete workflow runs can be cancelled automatically to prevent running workflows unnecessarily.
The feature is currently in beta. However, once it's stable enough, this can replace the need to rely on the 3rd party styfle/cancel-workflow-action
action.
Related information:
- Announcement post
- Updated GitHub Actions documentation
- https://github.com/styfle/cancel-workflow-action/issues/76
Some outstanding bug reports:
Change History (6)
This ticket was mentioned in PR #1217 on WordPress/wordpress-develop by ocean90.
4 years ago
#1
- Keywords has-patch added
#2
@
4 years ago
The reported bugs have been fixed by GitHub. Tested in PR #1217 and it seems to work so far.
4 years ago
#3
Just noting that before commit, I am going to add the following:
- Change the
cancel-in-progress
to atrue
value. - Going to add concurrency to the coding standards and compatibility workflows. These did not have a step to cancel previous runs, but I did not include that originally because they typically run in 1-2 minutes total, so the additional step was not really worth it. Where it's native now, doesn't hurt to add for when there is a backlog.
#4
@
4 years ago
- Keywords commit added
- Milestone changed from Future Release to 5.8
- Owner set to desrosj
- Status changed from new to assigned
4 years ago
#6
Merged into Core in https://core.trac.wordpress.org/changeset/50930.
Trac ticket: https://core.trac.wordpress.org/ticket/53080