Skip to content

An implementation of the Build Server Protocol for Bazel

License

Notifications You must be signed in to change notification settings

VirtuslabRnD/bazel-bsp

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

JetBrains team project TeamCity build status Bazel Steward badge

Bazel BSP

An implementation of the Build Server Protocol for Bazel.

Supported languages

  • Java
  • Kotlin
  • Scala
  • Python
  • Thrift
  • Rust (coming soon!)

Installation

Easy way (coursier)

  1. Have coursier installed
  2. Run in the directory where Bazel BSP should be installed:
cs launch org.jetbrains.bsp:bazel-bsp:<version> -M org.jetbrains.bsp.bazel.install.Install -- --targets //...

Please check release to find the newest available version 3. Add bsp generated folders to your .gitignore: .bsp and .bazelbsp

More difficult way (from sources)

Might be useful during development

Using install script

  1. Be inside this project
  2. Run bazel run //install -- <installer flags> (--help is available)

Using coursier

  1. Have coursier installed
  2. Be inside this project
  3. Change the project version - maven_coordinates attribute in the server/src/main/kotlin/org/jetbrains/bsp/bazel/BUILD file
  4. Publish a new version:
bazel run --stamp --define "maven_repo=file://$HOME/.m2/repository" //server/src/main/kotlin/org/jetbrains/bsp/bazel:bsp.publish
  1. Enter directory where Bazel BSP should be installed
  2. Install your version:
cs launch -r m2Local org.jetbrains.bsp:bazel-bsp:<your version> -M org.jetbrains.bsp.bazel.install.Install

Project Views

In order to work on huge monorepos you might want to specify directories and targets to work on. To address this issue, Bazel BSP supports (partly) the Project Views introduced by Google.

Check project view readme for more info.

Tests

End-to-end tests

e2e directory contains end-2-end tests that check various scenarios of server usage.

Tests are marked as manual so they won't be executed on bazel test //...

bazel test //e2e:<test name>_bazel_<bazel version> - to run a specific test (to see all possible tests, check the e2e/BUILD file), e.g. bazel test //e2e:sample_repo_test_bazel_6_3_2

Unit tests

Run bazel test //... to execute all the unit tests.

Contributing

Want to contribute? Great! Follow these rules.

About

An implementation of the Build Server Protocol for Bazel

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Kotlin 85.4%
  • Starlark 9.4%
  • Java 4.7%
  • Other 0.5%