Skip to content

ci: reduce workflow overhead - #3221

Draft
kevinjqliu wants to merge 1 commit into
apache:mainfrom
kevinjqliu:kevinjqliu-merge-queue-review
Draft

kevinjqliu wants to merge 1 commit into
apache:mainfrom
kevinjqliu:kevinjqliu-merge-queue-review

Conversation

@kevinjqliu

@kevinjqliu kevinjqliu commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Grouping a few changes together in this PR. Overall, this helps improve CI and merge queue.

  • Change max_entries_to_build from 1 to 2. This allows merge queue to run in parallel
  • Move a few lightweight jobs to run on ubuntu-slim: ASF allowlist check, stale maintenance, and the nightly version timestamp job
  • Add concurrency setting to cancel redundant runs in the same PR

Keep the main runs for hydrating caches unchanged.

Follows the Python workflow-overhead improvements.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

@dannycjones dannycjones left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Generally LGTM.

I'm inclined to remove the concurrency group unless it has a substantial reduction on wasted work, in the interest in avoiding complexity in workflow definitions.

Comment on lines +30 to +32
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
cancel-in-progress: true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we really see multiple runs sharing the same ref and event?

What's the trigger?

Comment thread .asf.yaml
check_response_timeout_minutes: 90
grouping_strategy: ALLGREEN
max_entries_to_build: 1
max_entries_to_build: 2

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not against more, conflicts are rare-ish.

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.

2 participants