Skip to content

Using j4rs in Github Actions #156

@dickermoshe

Description

@dickermoshe

This is most likely not a bug in j4rs, however I'm wondering what can be done to solve this.

Using the default actions-rust-lang/setup-rust-toolchain@v1 github action provides a caching layer which significantly improves the speed of subsequent Github Action runs. This caching is enabled by default

It seems that the jassets folder is not included in this cache. However, this does not trigger a rebuild of the crate. Therefor I'm seeing this error on subsequent runs of CI:

called `Result::unwrap()` on an `Err` value: GeneralError("Can not find jassets directory")

There are 2 approaches here:

  1. Force a rebuild of j4rs if the jassets folder is not found
  2. Manually include the jassets folder in caching.

This has been a pain to debug, so at least this issue will help someone else trying to figure out why their CI is failing. But only after the 2nd run.

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