Skip to content
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.

Sign up for GitHub

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

Jump to bottom

incompatible_auto_exec_groups #17134

Open
comius opened this issue Jan 4, 2023 · 2 comments
Open

incompatible_auto_exec_groups #17134

comius opened this issue Jan 4, 2023 · 2 comments
Assignees
@kotlaja
Labels
incompatible-change Incompatible/breaking change migration-ready Incompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green not stale Issues or PRs that are inactive but not considered stale P2 We'll consider working on this in future. (Assignee optional) team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts

Comments

@comius
Copy link
Contributor

comius commented Jan 4, 2023 •
edited by kotlaja

Flag: --incompatible_auto_exec_groups
Available since: Bazel 7
Flipped in: not yet
Planner removal: not yet

Current status
Implemented and almost ready to flip in Bazel@Head.

Short summary
Automatic execution groups select an execution platform for each toolchain type. In other words, one target can have multiple execution platforms without defining execution groups. Migration requires setting a toolchain parameter inside ctx.actions.{run, run_shell} for actions which use tool or executable from a toolchain.

More information
@comius comius added P2 We'll consider working on this in future. (Assignee optional) incompatible-change Incompatible/breaking change team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts labels Jan 4, 2023
@github-actions
Copy link

github-actions bot commented Feb 9, 2023

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 30 days. It will be closed in the next 7 days unless any other activity occurs or the "not stale" label is added.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 9, 2023
@keertk keertk added not stale Issues or PRs that are inactive but not considered stale and removed stale Issues or PRs that are stale (no activity for 30 days) labels Feb 9, 2023
@fmeum
Copy link
Collaborator

fmeum commented Feb 9, 2023

@keertk Not stale

@meteorcloudy meteorcloudy changed the title --incompatible_auto_exec_groups incompatible_auto_exec_groups May 8, 2023
@comius comius added the migration-ready Incompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green label Sep 8, 2023
@kotlaja kotlaja mentioned this issue Oct 30, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kotlaja kotlaja

Labels
incompatible-change Incompatible/breaking change migration-ready Incompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green not stale Issues or PRs that are inactive but not considered stale P2 We'll consider working on this in future. (Assignee optional) team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@comius @fmeum @kotlaja @keertk