Skip to content

Let Starlark executable rules specify their environment#15750

Closed
ckolli5 wants to merge 2 commits intobazelbuild:release-5.3.0from
ckolli5:ck/let-starlark-executable-rules-specify-their-env
Closed

Let Starlark executable rules specify their environment#15750
ckolli5 wants to merge 2 commits intobazelbuild:release-5.3.0from
ckolli5:ck/let-starlark-executable-rules-specify-their-env

Conversation

@ckolli5
Copy link
Copy Markdown

@ckolli5 ckolli5 commented Jun 27, 2022

The new RunEnvironmentInfo provider allows any executable or test
Starlark rule to specify the environment for when it is executed, either
as part of a test action or via the run command.

Refactors testing.TestEnvironment to construct a RunEnvironmentInfo and
adds a warning (but not an error) if the provider constructed in this
way is returned from a non-executable non-test rule. If a
RunEnvironmentInfo is constructed directly via the Starlark constructor,
this warning becomes an error.

Fixes #7364
Fixes #15224
Fixes #15225

Closes #15232.

PiperOrigin-RevId: 448185352

fmeum and others added 2 commits June 27, 2022 12:41
The new RunEnvironmentInfo provider allows any executable or test
Starlark rule to specify the environment for when it is executed, either
as part of a test action or via the run command.

Refactors testing.TestEnvironment to construct a RunEnvironmentInfo and
adds a warning (but not an error) if the provider constructed in this
way is returned from a non-executable non-test rule. If a
RunEnvironmentInfo is constructed directly via the Starlark constructor,
this warning becomes an error.

Fixes #7364
Fixes #15224
Fixes #15225

Closes #15232.

PiperOrigin-RevId: 448185352
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants