Skip to content

[chore](build) Reduce redundant Actions on branch-4.1 - #68025

Open
hello-stephen wants to merge 3 commits into
branch-4.1from
ci/slim-release-actions-41
Open

hello-stephen wants to merge 3 commits into
branch-4.1from
ci/slim-release-actions-41

Conversation

@hello-stephen

@hello-stephen hello-stephen commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Background

Release-branch GitHub Actions are frequently queued, including redundant post-merge runs and a thirdparty change detector on unrelated PRs.

Changes

  • Remove the duplicate Check Large File push trigger; keep pull_request_target.
  • Remove the legacy Need_2_Approval workflow. The branch's Code Owner approval policy remains the merge gate.
  • Start Build Third Party Libraries on PRs only when its relevant inputs change. Keep workflow_dispatch and issue_comment triggers.

Scope note

Code Checks is unchanged; its push trigger optimization is deferred for separate review.

External Regression's regression-test/pipeline/external/conf/fe.conf is excluded from both the PR entry filter and the old focused test filter. A change to that file alone will no longer trigger Thirdparty Script Test or its ADBC JNI assertion. The assertion still runs when a thirdparty-related change triggers the script test; this PR does not move it to another workflow.

Validation

  • actionlint passed for all edited workflow files (excluding pre-existing inline shellcheck and old-runner warnings).
  • git diff --check passed.
  • No required GitHub check on branch-4.1 is path-filtered by this PR.

No TeamCity pipeline or branch governance configuration is changed.

Limit release-branch Code Checks push runs to shell-script changes, remove the duplicate large-file push run and obsolete two-approval workflow, and path-filter the thirdparty PR workflow. Preserve existing PR, comment, and manual triggers.
@hello-stephen

Copy link
Copy Markdown
Contributor Author

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@mbien

mbien commented Sep 15, 2026

Copy link
Copy Markdown
Member

@hello-stephen also: consider using ubuntu-slim for short running actions like

runs-on: ubuntu-latest
steps:
- name: "Do nothing. Only trigger corresponding workflow_run event"
run: echo

it would come with less overhead since it runs in a container.

…triggers

Remove the regression-only FE config from both the PR entry path filter and the existing focused test change filter. Thirdparty-related changes still run the script test, including its ADBC configuration assertion.
Restore the original Code Checks triggers. The shell filename filter could miss extensionless shell scripts, so this PR retains only the confirmed release-branch Action reductions.
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