Skip to content

[FLINK-39928][ci] If there are changes in tests only then skip non related CI jobs in GHA#28433

Open
snuyanzin wants to merge 1 commit into
apache:masterfrom
snuyanzin:flink39928
Open

[FLINK-39928][ci] If there are changes in tests only then skip non related CI jobs in GHA#28433
snuyanzin wants to merge 1 commit into
apache:masterfrom
snuyanzin:flink39928

Conversation

@snuyanzin

@snuyanzin snuyanzin commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

What is the purpose of the change

The main idea: if there are only changes in tests, then skip non related jobs in GHA

for instance: if there is a test change in module table then skip others
if there are test changes in module core and table, then run jobs only for these 2
if there is a not only test change in any place then run everything as before
(examples in my fork

  1. changes only in tests of table module: https://github.com/snuyanzin/flink/actions/runs/27491394160
  2. changes in tests in table and formats https://github.com/snuyanzin/flink/actions/runs/27491450535
  3. changes in tests table, formats and e2e https://github.com/snuyanzin/flink/actions/runs/27491962097
  4. changes in e2e only https://github.com/snuyanzin/flink/actions/runs/27491434907
  5. changes in non test code https://github.com/snuyanzin/flink/actions/runs/27491407658 )

Brief change log

GHA

Verifying this change

GHA

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable)

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)


# Drift guard: a module added/removed inside an existing list is fine (lists are sourced),
# but a new/renamed/removed MODULES_* list or stage would misroute silently -> full matrix.
assert_no_stage_sh_drift() {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

fallback in case of for instance a new module added or removed or renamed

@flinkbot

flinkbot commented Jun 13, 2026

Copy link
Copy Markdown
Collaborator

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

Comment on lines +84 to +87
add core "${MODULES_CORE}"
add table "${MODULES_TABLE}"
add connect "${MODULES_CONNECTORS}"
add tests "${MODULES_TESTS}"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

based on stage.sh

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