Bazel
JetBrainsJetBrains · v—
Bazel by JetBrains for IntelliJ IDEA Main features Open Bazel projects in IntelliJ IDEA Supports Java and Kotlin Build, run, test, debug Bazel ta rgets Starlark syntax, completion, navigation support Starlark debugging Run and debug tests running in Bazel To learn more about how to use the features, please check t
Rating distribution
Reviews 8
This is the bazel plugin we've all been waiting for. It actually really works and is pretty seamless across multiple languages. I hope they continue to add the remaining languages jetbrains supports. this is a killer feature, much better than vscode.
Amazing. I was very long time user of maven/gradle. Bazel was something new to me. And as of now it looks as one of the best build ecosystems. Glad to see great plugin which matches overall Intellij platform and works organically with it rather than standing somewhere aside. Keep it up and keep on improving and adding even more features
At last we can use Bazel in Intellij in a native way. Whoever wrote Google Bazel Plugin have no idea how IJ works and don't really care about UX. IJ is all about usability and Jetbrains Bazel Plugin is a huge leap toward making Bazel properly supported in IJ.
Just what I expect from JetBrains, a well integrated plugin to the JetBrains ego system. Manages the project structure much more like other build systems, making it easier to understand the project for developers.
I like it so far. Need to support starlark language.
I like the plugin very much. I would like to see coverage runs of the several tests, such that I can see the coverage of the testcases.
I like the new syntax highlight and that's basically it. There are way too many things that do not work with this new plugin. For starters: "select opened file" button is broken no partial resync no UI support for running rules like container_structure_test or others (while support for running some useless ones was introduced)
Performance is definitely worse on a bigger project. Hot replacement shows No classes to reload, but then reload. There is no way to specify --local_cpu_resources=HOST_CPUS-1 to avoid performance degradation during build.
Similar in “Build”
File Watchers
JetBrains
Bazel for IntelliJ (legacy)
JetBrains
GitHub Actions Manager
d-software-inc
Gradle
JetBrains
Just
5f47aa04-3398-4eea-98f1-d27c0a115f9b
SBT
80c1d67d-878a-4c82-b04d-9ed0f45c876d