Skip to content

Automated deployment of player services to production #21

Description

@JannikAlx

Should follow after the naming conventions are done. My first approach would be an automated deployment cycle, which checks every x minutes if there is a new version available and if so, deploys it. This should be dynmaic to cover every player repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    devopsChanges to build pipeline or infrastructure

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions