Skip to content

Store active build status as assets and use it to sync jobs #57

Open
@lazka

Description

@lazka

As partly suggested by @MehdiChinoune we could try to sync the build jobs somewhat to avoid duplicated builds:

  • Have a new dummy release similar to the "failed" status
  • When a build starts upload a json file containing:
    • the job id, so we can check if the build is still active
    • a html log url, so we can show this on packages.msys2.org

This would allow us to build every build type on every job and scale better.

edit: (I wonder if there is a maximum length for release asset labels.. it could be used to store some json)

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