Skip to content

Roborazzi 1.56.0 caches golden_file_path as absolute, invalid after project move #791

@m0jOrty

Description

@m0jOrty

Description:

  • Roborazzi writes golden_file_path as an absolute path that includes the project folder.
  • After copying/moving the project (e.g., to a different CI workspace), the cached path becomes invalid.
  • This impacts verifyRoborazzi and makes Gradle’s test build cache unusable after project move. Apparently the testReleaseUnitTest task cannot be cached
  • Setting PathSensitivity.RELATIVE externally did not help.

Expected behavior:

  • Cache should be portable: store golden_file_path as a relative path (e.g., relative to roborazzi.outputDir or project/module root), or resolve paths relative to the current context on read.

Environment:

  • Roborazzi version: 1.56.0

Attempts:
We have tried to use the the following without success, this also creates the absolute path:
roborazzi.record.filePathStrategy=relativePathFromRoborazziContextOutputDirectory

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions