You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.
In a comment, @ulfjack mentioned that an action can be marked as "nosandbox". This is not documented anywhere that I can find. Can you add it to the web page?
All the documented tags are copied to the corresponding actions, and from there to the corresponding spawns. I have a pending change to update the docs.
In a comment, @ulfjack mentioned that an action can be marked as
"nosandbox"
. This is not documented anywhere that I can find. Can you add it to the web page?I'm pretty sure, from looking at the code, that this is a marker that can be put in the
"execution_requirements"
forctx.action.run()
orctx.actions.run_shell()
(or the older, deprecatedctx.action()
). For each of those, underexecution_requirements
, it says, "information for scheduling the action. See tags for useful keys," and the word "tags" is a a (currently broken) link to https://docs.bazel.build/versions/master/be/common-definitions.html#common-attributes.Two things:
execution_requirements
and a rule'stags
really the same thing? If not, then they need to be treated separately in the docs.nosandbox
to the appropriate place in the docs, wherever that may be?The text was updated successfully, but these errors were encountered: