Skip to content

Changes in cache configuration does not invalidate artifacts #369

@Tammo0987

Description

@Tammo0987

Affected version

1.2.0

Bug description

Hi,
I currently try to create a configuration for the maven build cache extension. Within that process I had some broken artifacts. Then I changed fixed configuration, but the extension did always restore the broken artifacts, because I he config is not included into the hash. This seems to be wrong for me.

I did found some workaround, with copying my configuration in a non hidden directory and specify that’s as part of my inputs, but it’s rather complicated. I would expect, that at least parts of the config will affect the hash calculation of the artifacts. Or that this usecase/limitation is documented.

P.S. I also thought, it is not explicitly stated in the documentation, that hidden files can’t be included as part of the inputs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions