[JIRA] (OVIRT-1602) [RFE] allow passing a gerrit link to ovirt-system-tests_manual

Sunday, 20 August 2017

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

------------=_1503237983-11245-294
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

Barak Korren commented on OVIRT-1602:
-------------------------------------

This short-cut had been asked for in 100,000 variations.

I think the best approach will be to just run OST tests per-patch (aka "patch
gating").

A slightly less optimal approach would be to add a "ci please test-system"
command in Gerrit.

This approach means we now have the make OST know how to build, that is very sub optimal
IMO.

...
 [RFE] allow passing a gerrit link to ovirt-system-tests_manual
 --------------------------------------------------------------

                 Key: OVIRT-1602
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1602
             Project: oVirt - virtualization made easy
          Issue Type: By-EMAIL
            Reporter: Yedidyah Bar David
            Assignee: infra

 Hi all,
 How about $subject?
 So that when ovirt-system-tests_manual sees a gerrit link supplied in
 CUSTOM_REPOS, it will do by itself 'ci please build' (extra points for
 checking if that's already done and reusing) and use the resultant
 build as if that build itself was supplied in CUSTOM_REPOS, thus
 freeing the user from doing that? I find myself many times running 'ci
 please build' only to later wait until it finished and then pass that
 to ovirt-system-tests_manual. For projects that are very quick to
 build, that's a bit tedious, but not too much. But for engine builds,
 that take somewhat longer, I often forget this and come back later. It
 would have been nice to be able to do this in a "single shot".
 Thanks,
 -- 
 Didi 

--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)

------------=_1503237983-11245-294
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jir...
]</pre>
<h3>Barak Korren commented on OVIRT-1602:</h3>
<p>This short-cut had been asked for in 100,000 variations.</p>
<p>I think the best approach will be to just run OST tests per-patch (aka
&quot;patch gating&quot;).</p>
<p>A slightly less optimal approach would be to add a &ldquo;ci please
test-system&rdquo; command in Gerrit.</p>
<p>This approach means we now have the make OST know how to build, that is very sub
optimal IMO.</p>
<blockquote><h3>[RFE] allow passing a gerrit link to
ovirt-system-tests_manual</h3>
<pre>     Key: OVIRT-1602
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1602
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>Hi all, How about $subject? So that when ovirt-system-tests_manual sees a gerrit
link supplied in CUSTOM_REPOS, it will do by itself &lsquo;ci please build&rsquo;
(extra points for checking if that's already done and reusing) and use the resultant
build as if that build itself was supplied in CUSTOM_REPOS, thus freeing the user from
doing that? I find myself many times running &lsquo;ci please build&rsquo; only to
later wait until it finished and then pass that to ovirt-system-tests_manual. For projects
that are very quick to build, that's a bit tedious, but not too much. But for engine
builds, that take somewhat longer, I often forget this and come back later. It would have
been nice to be able to do this in a &ldquo;single shot&rdquo;. Thanks,
&mdash; Didi</p></blockquote>
<p>&mdash; This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)</p>

------------=_1503237983-11245-294--

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

[JIRA] (OVIRT-1602) [RFE] allow passing a gerrit link to ovirt-system-tests_manual