✨ feat(pkg): cache external packaging env build across envs#3790
Merged
gaborbernat merged 1 commit intotox-dev:mainfrom Feb 20, 2026
Merged
✨ feat(pkg): cache external packaging env build across envs#3790gaborbernat merged 1 commit intotox-dev:mainfrom
gaborbernat merged 1 commit intotox-dev:mainfrom
Conversation
gaborbernat
added
feature:change
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
1 participant
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.
When using
package = externalwith a sharedpackage_env, the build commands run once per test environment that depends on it, rebuilding an identical package each time. For projects compiling C extensions or running complex build pipelines, this wastes significant time — often several minutes per redundant build.🚀 The built package path is now cached after the first successful build within a session. Subsequent test environments that share the same external packaging env skip the build entirely and reuse the already-built artifact. Per-environment extras and dependencies are still resolved individually, so environments with different
extrasconfigurations continue to get the correct dependency set.This mirrors the caching behavior that
wheel_build_envalready provides for PEP-517 wheel builds, extending the same optimization to external packaging workflows.Fixes #2729