Skip to content

check fails with error when no versions exist #33

@designed4device

Description

@designed4device

When no version exists in repository (prior to first put), the check will return error message.
I believe this should instead "fail gracefully" and show no versions instead of error, or at the very least show a more meaningful error.

resource script '/opt/resource/check []' failed: exit status 22

stderr:
curl: (22) The requested URL returned error: 404 path/to/artifact/maven-metadata.xml

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions