The Gatekeeper

Diagram

The gate.sh execution loop

The core of the gate is the part function, which encapsulates the execution of a command and its reporting gate.sh:43-85. To maintain honesty in environments where certain toolchains are missing, the script utilizes the SKIPPED_CODE (77) convention gate.sh:24-35. This allows the script to report that a part was "skipped" rather than "failed," preventing a machine without a Go toolchain from reporting a broken Go client when the developer simply hasn't installed the necessary dependencies gate.sh:132-142.

The jvm and client lifecycle

The execution follows a strict dependency chain to ensure efficiency and correctness. The jvm part runs the core Gradle checks gate.sh:101. For any client module, the gate first executes the client's own internal gate.sh gate.sh:109-114. A client's conformance check is only triggered if its own unit tests pass and a conformance binary exists gate.sh:117-120. To prevent redundant work during the Docker-based image build, the BOOBLIK_SKIP_GATE environment variable is used to skip the redundant execution of the gate within the containerized environment gate.sh:39-40.

The conformance check

The final and most heavy-weight stage is the conformance check, which validates the reference client against a live broker gate.sh:124. This stage is unique because it requires both a Docker daemon to run the broker and a Gradle environment to manage the test orchestration. It is the only part of the gate that performs an end-to-end verification of the protocol by running a client against a real, running instance of the broker gate.sh:119.

The check job and the image job separation

The CI architecture splits the verification into two distinct jobs in build.yml:14-90. The check job runs on a standard runner to perform JVM-based tests and smoke tests without requiring Docker build.yml:35-48. The image job is separated because it requires a Docker daemon and is responsible for verifying the actual containerized process, including the six specific JVM profile flags docker-smoke.sh:73-84. This separation ensures that environmental issues in the Docker layer do not mask code-level failures in the JVM layer.

Key files

Behaviour that surprises

• The part function uses a case statement to handle exit codes, ensuring that a command's failure is captured correctly even when using PIPESTATUS in a pipeline gate.sh:65-67.
• The gate.sh script uses a trap to ensure that the temporary directory used for storing logs is cleaned up upon exit gate.sh:26.
• In ci/docker-smoke.sh, the script uses a for loop to iterate through a specific list of JVM flags to ensure the runtime profile matches the measured requirements docker-smoke.sh:76-83.