[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash

Sunday, 29 October 2017

This is a multi-part message in MIME format...

------------=_1509291601-21586-158
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [
https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jir...
] 

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)

------------=_1509291601-21586-158
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jir...
]</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>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)</p>

------------=_1509291601-21586-158--

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011