Control Artifact uploads based on rules for releases - Githubissues

ynput / ops-repo-automation

Collection of automation tools and github-workflows for Ayon related repositories.

0 stars 0 forks source link

Control Artifact uploads based on rules for releases #6

Open philnewm opened 2 months ago

philnewm commented 2 months ago

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the enhancement you have in mind and explain what the current shortcomings are?

Artifacts crated by a release trigger will need to be uploaded to different places.

Whats needs to be defined

Which kinds of artifts can exist?
Which artifacts needs to go where?
What are the rules for these?
How will they need to be handled by a release trigger?

How would you imagine the implementation of the enhancement?

A release trigger could have a mapping for any kind of possible artift and what to do with it. This mapping would need to be based on rules.

Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response