ci: run selected example charm integration tests on PRs - #2655
Open
dwilding wants to merge 1 commit into
Open
Conversation
dwilding
force-pushed
the
example-charm-integration-tests
branch
from
July 21, 2026 02:47
e5cee02 to
75ac2d7
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This was referenced Jul 21, 2026
dwilding
force-pushed
the
example-charm-integration-tests
branch
2 times, most recently
from
August 26, 2026 02:57
2cada15 to
2e9701e
Compare
dwilding
marked this pull request as ready for review
August 28, 2026 00:42
dwilding
force-pushed
the
example-charm-integration-tests
branch
from
August 28, 2026 00:48
2e9701e to
e88dbd5
Compare
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
2 participants
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.
This PR adds a workflow that runs our example charm integration tests on PRs.
It largely duplicates the existing "Example Charm Integration Tests" workflow that runs on a weekly schedule. The key difference is that the new workflow uses a "detect-changes" job to select which integration test jobs to run, based on exactly which example charms have changed. This avoids needing a separate path-filtered workflow for each charm.
I explored reducing redundancy by extracting the common parts of the scheduled workflow and the new workflow, but the result was hard to understand. I think a bit of duplication is better in this case. Our set of example charms shouldn't change much in future.
Sample run in my fork, where only the
k8s-*charms have changed.