Skip to content

[upload-charm] Add input for specifying retry strategy #104

Description

@sed-i

Enhancement Proposal

Occasionally (frequently?) charmhub has an outage, and the upload-charm action fails with e.g.

Wrong status code from server (expected=201, got=504)
Full execution log: '/home/runner/.local/state/charmcraft/log/charmcraft-20230908-013552.678390.log'
Error: The process '/snap/bin/charmcraft' failed with exit code 1
Error: Error: The process '/snap/bin/charmcraft' failed with exit code 1

It could be handy if the action supported a retry strategy to have the workflow complete in cases of short term charmhub glitches.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    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