[
https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35237#comment-35237
]
eyal edri commented on OVIRT-1717:
----------------------------------
This requires keeping a hash/mapping of each project rpm to a source repo,
maintaining permissions for a specific user to tag any project ( and keeping
track on new projects,etc.. ), and to what purpose?
I'm not sure what is the reason behind this request, but won't it be irrelevant
once we move to patch gating? ( which should happen in the near future ), which
means any merged patch is basically passing OST and tested?
> When a component build passes OST, tag its git hash
> ---------------------------------------------------
>
> Key: OVIRT-1717
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: oVirt CI
> Reporter: danken
> Assignee: infra
> Labels: change-queue, standard-ci
>
> Tagging the source git would make it easier for me to tell if a specific git
> commit is already tested by OST and available for QA.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
