Barak Korren updated OVIRT-2033:
    Epic Link: OVIRT-2184  (was: OVIRT-400)

> Provide a "tagging" mecahnism for transactional mirrors.
> --------------------------------------------------------
>                 Key: OVIRT-2033
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: CI Mirrors
>            Reporter: Barak Korren
>            Assignee: infra
> Right now when using the CI mirrors, one can either:
> # Use the latest snapshots from all mirrors as mock_runner and all the jobs 
> do.
> # Use a specific snapshot by using the direct URL to it as we do on slaves.
> It is desirable to be able to mark or tag specific mirror snapshots for 
> various uses. The primary use for this is to track which mirror snapshots 
> have been tested successfully by the change queue in a similar fashion to the 
> way we track passing packages by storing them in the 'tested' repo. The 
> motivation behind doing this is described in OVIRT-1444

This message was sent by Atlassian Jira
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
List Archives: 

Reply via email to