Repository navigation
refactor(project): Support cache-exempt build stages - #1680
Open
RandomByte wants to merge 3 commits into
Open
RandomByte wants to merge 3 commits into
RandomByte wants to merge 3 commits into
Conversation
Some tasks must execute on every build because their inputs or side effects are outside the resource model. Allow setTasks to mark their stages as exempt with a false cacheable flag. Skip cache lookups and writes for exempt stages while retaining their request indices and written-path accounting. Disable the project result cache and make isFresh honor that state across repeated builds. Other stages remain cacheable. Cover stage lookup, persistence, and repeated validation with one cache instance in the cache tests.
Custom tasks below Specification Version 5.0 may perform untracked I/O. Run them on every build. From 5.0, allow task descriptors to opt out by setting cache to false, and validate that the cache flag is a boolean. Share the exemption rule between TaskDefinitions and TaskRunner. Apply composeTaskList before disabling the project result cache, so excluded tasks preserve caching. Honor wildcard selection and repeated task configurations. Warn once per process for legacy tasks and log explicit opt-outs at verbose level. Include unit tests and fixtures for both exemption cases. Integration tests verify repeated execution, cached sibling tasks, and result-cache reuse when the exempt task is excluded.
Document the legacy-task exemption and the descriptor opt-out in the incremental-build architecture reference. Describe stage execution, result-cache suppression, and the warning behavior.
RandomByte
marked this pull request as ready for review
October 27, 2026 07:37
This branch has not been deployed
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.
Some tasks must execute on every build because their inputs or side effects
are outside the resource model. Allow setTasks to mark their stages as
exempt with a false cacheable flag.
Custom tasks below Specification Version 5.0 may perform untracked I/O.
Run them on every build. From 5.0, allow task descriptors to opt out by
setting cache to false, and validate that the cache flag is a boolean.