Validate artifacts
validate artifacts - Validate that build artifacts exist for a module and its dependencies
Validate that build artifacts exist for a module and all transitive dependencies.
This command checks that all required build artifacts are present in out/build/ for the specified module and all modules it depends on. This ensures that the build→test flow has all necessary artifacts before running tests.
The validation includes: - Target module artifacts (executables, files, directories, etc.) - All transitive dependency artifacts (recursive check, unless --skip-depm) - Platform-specific artifacts for current platform (or all if built) - Marker files for modules with no traditional build outputs
Validation failures indicate missing artifacts that must be built before testing.
Flags
| Flag | Description |
|---|---|
--skip-depm (default: false) |
Skip validation of transitive module dependencies (for release workflows) |
--os (default: runtime.GOOS) |
Target OS for platform-specific artifacts |
--arch (default: runtime.GOARCH) |
Target architecture for platform-specific artifacts |
Notes
Expected Output:
Displays validation results for target module and all dependency artifacts. Exit code 0 if all artifacts present, non-zero if any missing. Shows detailed table with artifact counts and missing artifact paths.
Examples
validate artifacts eac-commands
validate artifacts r2r-cli --os linux --arch amd64
validate artifacts docs --skip-depm # Release context: skip module deps
See Also
Tutorials | How-to Guides | Explanation | Reference
You are here: Reference — information-oriented technical descriptions of the system.