<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35237#comment-35237 ]</pre>
<h3>eyal edri commented on OVIRT-1717:</h3>
<p>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?</p>
<p>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?</p>
<blockquote><h3>When a component build passes OST, tag its git hash</h3>
<pre> 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</pre>
<p>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.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzYS3r1Q939T2sgz3e-2FOcxqJ7IahXMC5szXVs7cpybF5JobVZaCpTZSGnAIMnAusobXGlnBJHAaJKFWyppVVlCxLUlfl4W03GLZHBa1R8ZrQhQ4rvpYMuM7M7fkqAWqFvTijL6M2dqUtKgDzhNMHaE-2Fm3SVFsOZmI-2Bd4H7pD7JOB5aIqUlOwqkDotZY9pqKpQIohNtpG5qxcqv9V0-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>