Build-tool-schemas

Build-tool-schemas is a utility that organises and translates data formats for OpenTelemetry.

  • Tools & Utilities
Build-tool-schemas is a utility that organises and translates data formats for OpenTelemetry. It ensures that different software systems speak the same language when tracking performance, allowing businesses to standardise how they monitor their digital services and troubleshoot issues more efficiently.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 24 days ago
Popular
3343 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
94no serious findings, CI, tests, OpenSSF Scorecard 8.6/10

Based on 4 of 5 factors.

GitHub stars
43
Open issues
4
Last commit
2026-10-27
Latest release
v0.26.0
License
Apache-2.0
Activity
declining

Checked 16 days ago - source: GitHub (open-telemetry/build-tools)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Name each step and give it a command In the Cloud Build file (the recipe for the build), every step needs an image name (the container that runs the step) plus the command to run using entrypoint or args (the program and its pieces). If those are missing or wrong, the step may do nothing or fail before your build finishes. source
  • Run steps in the order you need Cloud Build runs steps top to bottom, so put a build step before a push step and setup before anything that uses it. Reversing the order makes later steps fail because the image or files they expect don't exist yet. source
  • Replace example variables with real ones If you copy a sample, replace values like ${PROJECT_ID} and custom variables such as _PACKAGE, _LOCATION, or _REPOSITORY with your own. Otherwise the build can point to a missing project, registry, or image. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What can happen if a build step is missing required fields?

The step may do nothing or fail before the build finishes. Each step needs an image name and the command to run, using entrypoint or args.

In what order are build steps run?

Build steps run top to bottom. A setup or build step should come before steps that use its image or files.

What should be changed when copying a sample build configuration?

Replace example variables such as the project ID and custom package, location, or repository values with your own. Otherwise the build can point to a missing project, registry, or image.

What MSBuild error occurs when the SqlTasks target is missing?

MSBuild reports error MSB4226 saying Microsoft.Data.Tools.Schema.SqlTasks.targets was not found. It occurs while building a self-hosted GitHub runner image from a Dockerfile.

Answers sourced from docs.cloud.google.com, docs.cloud.google.com, docs.cloud.google.com, stackoverflow.com

Community

Collected 48 days ago - public community threads