Skip to content

Unify env vars for Utilities/bootstrap commands #8154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

MaxDesiatov
Copy link
Contributor

This is a prerequisite for enabling incremental builds when running ./Utillities/bootstrap build --release and ./Utilities/bootstrap test --release in a sequence.

Motivation:

Environment variables passed to swift-bootstrap from ./Utilities/bootstrap build and ./Utilities/bootstrap test commands unnecessarily differed slightly, which caused generated build manifests to be different. This precluded incremental builds when running these commands in a sequence one after each other, slowing down our CI jobs.

Modifications:

Moved env var computation logic to the existing get_swiftpm_env_cmd function in Utilities/bootstrap.

Result:

swift-bootstrap is consistently called with the same environment variables, ensuring that generated build manifests can be the same, eventually enabling incremental builds.

This is a prerequisite for enabling incremental builds when running `./Utillities/bootstrap build --release` and `./Utilities/bootstrap test --release` in a sequence.
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@MaxDesiatov MaxDesiatov merged commit 6ae005e into main Dec 4, 2024
5 checks passed
@MaxDesiatov MaxDesiatov deleted the maxd/unify-bootstrap-env branch December 4, 2024 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bootstrap Bootstrapping script & swift-bootstrap
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants