Bazel

Bazel-based mobile projects use a rebuild-based dev loop. Revyl detects Bazel workspaces by looking for MODULE.bazel, WORKSPACE.bazel, or WORKSPACE files. Because Bazel build targets and artifact paths vary per project, revyl init creates placeholder platform entries that you fill in with your specific build targets.

What `revyl init` shows

Detected: Bazel
  Workspace: MODULE.bazel
  Note: Revyl detected a Bazel workspace but cannot infer build targets automatically.
        Configure build.platforms.ios and/or build.platforms.android in .revyl/config.yaml.

Example configuration

build:
  system: Bazel
  platforms:
    ios:
      commands:
        - "bazel run //tools:generate_mobile_sources"
        - "bazel build //ios:MyApp -c dbg"
      output: "bazel-bin/ios/MyApp.app"
    android:
      command: "bazel build //android:app -c dbg"
      output: "bazel-bin/android/app.apk"

Kotlin Multi-platform (KMP)Atlas

Getting Started

Guides

CLI

Builds

Tests

Develop

Atlas

Integrations

Appendix

What `revyl init` shows

Example configuration

​What revyl init shows

​Example configuration

What `revyl init` shows

Example configuration