Make test-product retention configurable - #532
Draft
ianrahman wants to merge 1 commit into
Draft
Conversation
ianrahman
marked this pull request as draft
September 11, 2026 21:01
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 changed
testProductsMaxCountandtestProductsMaxAgeDaysproject configuration, withXCODEBUILDMCP_TEST_PRODUCTS_MAX_COUNTandXCODEBUILDMCP_TEST_PRODUCTS_MAX_AGE_DAYSenvironment overrides.xctestproductsretention from 100 bundles / 3 days to 3 bundles / 1 dayWhy
Source-based test runs stage a full
.xctestproductsbundle under the workspace storage directory. For multi-gigabyte test products, the previous 100-bundle default permits hundreds of gigabytes of retained data before count-based cleanup applies.Validation
3scanned,2deleted, newest retained)git diff --checkFixes #524.
AI assistance: Codex helped trace the retention lifecycle, implement the configuration surface, and run the available validation. The resulting diff and test evidence were reviewed before submission. (Though tbh I'm not a Typescript guy and this could use more experienced review for that reason.)