AlinsRan opened a new pull request, #2867:
URL: https://github.com/apache/apisix-ingress-controller/pull/2867
### Description
Twelve workflows run on every pull request push, but only four of them
(`apisix-e2e-test`, `apisix-conformance-test`, `benchmark-test`,
`kustomize-checker`) declare a concurrency group. The other eight keep every
superseded run alive, so a rebase or a follow-up commit leaves the previous
run's jobs queued and competing for the shared Apache Actions runner pool.
Queueing here is already the dominant cost. In a recent sample, a PR pushed
at
23:17 UTC did not get a single job scheduled until 00:33 UTC.
`spell-checker`,
which executes in seconds, took 76 minutes wall clock, all of it in the
queue.
Every job in that batch started inside the same 40-second window, which is
what
capacity being released in bulk looks like.
This PR adds the same concurrency group already used by the heavy workflows
to:
- `codeql-analysis.yml`
- `dependency-review.yml`
- `golangci-lint.yml`
- `license-checker.yml`
- `lint-checker.yml`
- `spell-checker.yml`
- `unit-test.yml`
- `yamllint-checker.yml`
`push-docker.yaml`, `release-drafter.yml` and `stale.yml` are deliberately
left
unchanged. They are not pull-request triggered, and cancelling them in
progress
could drop an image push or a release draft update.
The group key is `${{ github.workflow }}-${{
github.event.pull_request.number || github.ref }}`,
identical to the existing four, so runs are only ever cancelled by a newer
run
of the same workflow on the same PR or branch.
### Which issue(s) this PR fixes
Reduces runner contention on the shared Apache Actions pool. No functional
change to the controller.
### Checklist
- [x] I have explained the need for this PR and the problem it solves
- [x] I have explained the changes or the new features added to this PR
- [ ] I have added tests corresponding to this change
- [x] I have updated the documentation to reflect this change
- [x] I have verified that this change is backward compatible
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
