Skip to content

Define aliased tools as binaries #171

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 2 commits into from
Jan 16, 2023

Conversation

oliverlee
Copy link
Contributor

Define tools as sh_binary's instead of aliases to filegroups, allowing use with rules that expect files_to_run.executable attributes (e.g. https://github.com/erenon/bazel_clang_tidy).

@oliverlee
Copy link
Contributor Author

@rrbutani It looks like the failures in CI are unrelated to this change. Are these known to be flaky?

@rrbutani
Copy link
Collaborator

@oliverlee Yup, the external tests are flaky. There were some related changes recently that I think your branch is missing but even with those changes the external tests will still fail.

I wouldn't worry about it and this PR looks good to me but @siddharthab should take a look too (I'm not really an active maintainer of this repo anymore).

@siddharthab
Copy link
Contributor

Can you rebase your branch on the latest master? I think at least one of those failure is gone by now.

But independent of the test failure, I would not wrap the aliased file in a sh_binary. If one does not exist, maybe making a small custom rule would do the job.

Define tools as native_binary's instead of aliases to filegroups,
allowing use with rules that expect `files_to_run.executable`
attributes.
@siddharthab siddharthab merged commit b918438 into bazel-contrib:master Jan 16, 2023
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.

3 participants