[MINOR] ci: Add idp-basic test workflow#11075
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a dedicated GitHub Actions workflow to run the :plugins:idp-basic:test Gradle task, enabling module-scoped CI coverage for the idp-basic plugin.
Changes:
- Introduces
.github/workflows/idp-basic-test.ymlto run:plugins:idp-basic:teston push/PR and manual dispatch. - Uses
dorny/paths-filterplus a module existence check to avoid running the workflow when unrelated files change. - Uploads
plugins/idp-basictest reports as artifacts when the test job fails.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Collaborator
Author
|
@roryqi Could you please run this "ci" for me? |
roryqi
reviewed
May 13, 2026
| with: | ||
| filters: | | ||
| source_changes: | ||
| - plugins/idp-basic/** |
Contributor
There was a problem hiding this comment.
If you relies on core module, you should include core module here.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Code Coverage Report
|
Collaborator
Author
Got. could merge pr? THX. |
Abyss-lord
pushed a commit
to Abyss-lord/gravitino
that referenced
this pull request
May 20, 2026
### What changes were proposed in this pull request? This PR adds a dedicated GitHub Actions workflow for `:plugins:idp-basic:test`. It introduces: - a standalone `idp-basic` workflow under `.github/workflows/idp-basic-test.yml` - path filtering so the workflow mainly runs for `idp-basic` and build-related changes - `dockerTest=true` in the test step so the workflow is ready for multi-database execution when `idp-basic` backend tests are present - artifact upload for `plugins/idp-basic` test reports on failure ### Why are the changes needed? `idp-basic` currently does not have a dedicated module-level CI workflow. Adding one makes the module easier to validate independently and prepares CI coverage for future backend tests in this module. Fix: apache#11076 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? ```bash ./gradlew :plugins:idp-basic:test -PskipITs -PskipDockerTests=false -PskipWeb=true ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR adds a dedicated GitHub Actions workflow for
:plugins:idp-basic:test.It introduces:
idp-basicworkflow under.github/workflows/idp-basic-test.ymlidp-basicand build-related changesdockerTest=truein the test step so the workflow is ready for multi-database execution whenidp-basicbackend tests are presentplugins/idp-basictest reports on failureWhy are the changes needed?
idp-basiccurrently does not have a dedicated module-level CI workflow. Adding one makes the module easier to validate independently and prepares CI coverage for future backend tests in this module.Fix: #11076
Does this PR introduce any user-facing change?
No.
How was this patch tested?