Self-service onboarding in Hermetiq Cloud
Create or join a project in the hosted dashboard, then follow its Quickstart: download the project’s credential helper, issue your own credentials, and copy the Bazel configuration.
Connect Bazel build data to Hermetiq Cloud or your own deployment, secure credentials, and verify ingestion. Continue to executor provisioning for Managed Builds.
This guide connects Bazel build data to Hermetiq. To run actions on Hermetiq’s infrastructure, follow the Managed Builds setup path as well.
Before connecting a build, you need:
python3, plus the macOS Keychain or pass on Linux to hold your credentials.Create or join a project in the hosted dashboard, then follow its Quickstart: download the project’s credential helper, issue your own credentials, and copy the Bazel configuration.
Sign in to your organization’s Hermetiq URL, select an existing project, and obtain the project credential helper from your platform administrator.
tools/hermetiq-credential-helper and tools/set-build-metadata.sh at the workspace root, next to MODULE.bazel or WORKSPACE, make them executable, and commit them. The helper holds no secrets, so every clone and git worktree gets it.tools/hermetiq-credential-helper store once per machine. When it asks, click Copy credentials and paste the whole line it copies, {"client_id": "...", "client_secret": "..."}. It saves them in the macOS Keychain, or in pass on Linux..bazelrc block. Quickstart supplies the project ID, BEP and results endpoints, the credential-helper lines, build metadata, profile flags, and the optional remote cache.chmod +x tools/hermetiq-credential-helper tools/set-build-metadata.sh
git add tools/hermetiq-credential-helper tools/set-build-metadata.sh
tools/hermetiq-credential-helper storeInstalling Hermetiq in your own cluster first? Follow the on-prem installation guide, then return here to connect a build.
See Deployments for the supported topology and Administration for project and credential ownership.
In Hermetiq Cloud, the credential helper holds only the project ID and Hermetiq’s token endpoint. Each person and each CI system uses their own M2M client ID and secret, which the helper reads, in order, from the HERMETIQ_M2M_CLIENT_ID and HERMETIQ_M2M_CLIENT_SECRET environment variables, the macOS Keychain item hermetiq/<project-id>, or the pass entry of the same name.
.gitignore, and restrict its file permissions.If you kept the default isolated configuration, activate it with --config=hermetiq:
bazel build //... --config=hermetiqIf you chose global build entries instead, run your normal Bazel command. CI can use the same configuration once it has its own credentials.
In Hermetiq Cloud, an MCP-connected agent can also do the repository setup through the MCP setup workflow. You still issue and store your own credentials.
A recorded invocation confirms ingestion. It does not establish that actions ran remotely. For Managed Builds, continue with executor provisioning and configuration, then verify a remotely executed action.