chore: Collect test projects at CI runtime#1543
Merged
HofmeisterAn merged 5 commits intodevelopfrom Oct 3, 2025
Merged
Conversation
HofmeisterAn
added
the
chore
✅ Deploy Preview for testcontainers-dotnet ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Yes, makes sense. GH actions is a nightmare to debug ) |
Collaborator
Author
Luckily, we can test this pretty easily locally too. |
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.
What does this PR do?
This PR adds support for collecting test projects during CI runtime and creating the strategy on the fly. It automatically detects new test projects and adjusts the strategy as needed. For example, if only certain modules change, we don't have to build or test unrelated modules. It also lets us filter out unnecessary tests, reducing CI time, saving resources, and speeding up feedback.
This PR doesn't include the logic to filter out unrelated test projects yet. We'll add that in a separate PR. For now, projects just pass through the filter script /cc @digital88 WDYT?.
Why is it important?
-
Related issues