Skip to content

ci: cancel superseded PR runs and cap e2e parallelism - #13967

Open
oc-tmueller wants to merge 1 commit into
owncloud:masterfrom
oc-tmueller:ci/limit-runner-fan-out
Open

oc-tmueller wants to merge 1 commit into
owncloud:masterfrom
oc-tmueller:ci/limit-runner-fan-out

Conversation

@oc-tmueller

Copy link
Copy Markdown

Why

The owncloud org can run at most 60 standard GitHub-hosted runners at once, and every repo in the org
shares that limit. Every push to a PR here starts a full new "Test and build" run, and the previous run
keeps going.

What

  • Cancel superseded PR runs. The group is workflow + PR number. Push and tag runs are keyed on their
    own run_id, so they never cancel or replace each other. (GitHub allows only one pending run per group,
    so sharing github.ref would silently drop runs on quick consecutive pushes.)
  • Cap the e2e matrix at max-parallel: 4, down from 10.

Companion to owncloud/ocis#13453.

Trade-offs for review

  • _e2e.yml is reusable, so the cap applies to nightly and tag runs too, not only PRs.
  • check-tests-passed stays on always(). In a cancelled run it reports failure on the superseded commit.
    That's deliberate. With !cancelled() it would be skipped, which GitHub counts as a passing required
    check.
  • stable-12.3 keeps its own workflow file and needs a backport once this is merged.

🤖 Generated with Claude Code

The org shares 60 standard GitHub-hosted runners across all repos, and every
push to a PR started another full Test and build run while the previous one
kept going.

- Add a concurrency group to Test and build: a new push to a PR cancels that
  PR's previous run. Push and tag runs are keyed on their run id, so they
  never cancel each other.
- Cap the e2e matrix at 4 parallel jobs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: oc-tmueller <323649642+oc-tmueller@users.noreply.github.com>
@update-docs

update-docs Bot commented Nov 12, 2026

Copy link
Copy Markdown

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@CLAassistant

CLAassistant commented Nov 12, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@kw-security

kw-security commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants