Skip to content

[Bug]: Failures for OS-specific tools #79

Description

@Malcolmnixon

Description

A tool that only runs on one operating system might for example only define a command-{os} value leaving the generic command blank.

Unfortunately doing so results in an error ".versionmark.yaml(40,6): error: Tool 'xyz' must have a 'command' field"

Steps to Reproduce

  1. Define a .versionmark.yaml with a windows-only tool using the command-win syntax
  2. Run the VersionMark on windows
  3. Observe VersionMark reports errors about missing 'command' field

Expected Behavior

VersionMark should support os-specific commands, and function on that OS; but then fail if trying to capture that tool on an unsupported os.

Actual Behavior

It seems not providing a generic 'command' is unsupported even when a generic 'command' isn't possible.

Code Sample

Tool Version

1.4.0

.NET Version

.NET 8

Operating System

Windows 11

Additional Context

No response

Checklist

  • I have searched existing issues to ensure this is not a duplicate
  • I have provided a clear description of the problem
  • I have included steps to reproduce the issue

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions