Skip to content

Bug: The openjd run command does not handle relative paths correctly #25

Description

@mwiebe

Expected Behaviour

  1. If a relative path is a default parameter to a job template, it should treat the path as relative to the location of the job template.
  2. If a relative path is provided as a job parameter (e.g. -p InputSceneFile=../path/to/car_render.blend, it should treat the path as relative to the current CWD.

Current Behaviour

The relative path is untouched in how the job is run, so it shows up as a relative path in the template substitution. That means that in both the case of a job template parameter default, and a job parameter provided externally, the path is treated as relative to whatever the CWD happens to be when the path is used inside the job template script.

Reproduction Steps

No response

Code Snippet

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions