.bazelrc

# Enable runfiles on all platforms. Runfiles are on by default on Linux and MacOS but off on
# Windows.
#
# If you are developing on Windows, you must either run bazel with administrator privileges or
# enable developer mode. If you do not you may hit this error on Windows:
#
#   Bazel needs to create symlinks to build the runfiles tree.
#   Creating symlinks on Windows requires one of the following:
#       1. Bazel is run with administrator privileges.
#       2. The system version is Windows 10 Creators Update (1703) or later
#          and developer mode is enabled.
#
# Docs: https://bazel.build/reference/command-line-reference#flag--windows_enable_symlinks
# Docs: https://bazel.build/reference/command-line-reference#flag--enable_runfiles
startup --windows_enable_symlinks
build --enable_runfiles

# Allow to run Bazel without pre-installed JDK.
# Docs: https://bazel.build/reference/command-line-reference#flag--java_runtime_version
build --java_runtime_version=remotejdk_21 --tool_java_runtime_version=remotejdk_21

# Not ready for the MODULE.lock file yet, as of Bazel 7.0.0 there are still some stability issues.
common --lockfile_mode=off

# Ignore timeout different between JRuby and MRI.
test --test_verbose_timeout_warnings=false

# JRuby needs $HOME for File#expand_path to work: https://github.com/jruby/jruby/issues/5661.
# TruffleRuby needs $HOME too: https://github.com/oracle/truffleruby/issues/2784.
build --action_env=HOME
test --test_env=HOME

# Allows to run tests with rdbg bundled with Ruby 3.1:
# 1. Add breakpoint with `debugger`.
# 2. Run tests: `bazel test --config debug spec:add`.
# 3. Connect to debugger: `bazel-gem/external/ruby/dist/bin/rdbg -A`.
test:debug --run_under="@ruby//:rdbg --nonstop --open --command"