Skip to content

Cycle info in status should not depend on job inputs #72

Open
@lazka

Description

@lazka

The cycle info written to the status file should depend on

  • the actual cycles
  • the built packages
  • the hardcoded cycle breakers in the code

but not on the job inputs, otherwise it will alternate between different states depending on which workflow wrote the status file.

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