<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35973#comment-35973 ]</pre>
<h3>sbonazzo commented on OVIRT-1918:</h3>
<p>bq. Maybe we need to use always the official release repo as fallback to tested?</p>
<p>I don't think so. Tested repo should not require official release repo. Official release should be eventually generated from tested repo, not the other way around.</p>
<p>bq. In case a specific PKG failed to build and it's maintainer didn't make sure bq. to fix it and redeploy, it makes sense to get missing pkgs from latest bq. official release, as we do in OST.</p>
<p>How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published.</p>
<p>bq. Once the maintainer of the project will build a new image and it passes, it bq. will be in tested.</p>
<p>That's not always true. I had several packages that required me to issue “ci re-merge please” multiple times before getting to tested repo without any code change on the project itself.</p>
<blockquote><h3>Single project tests in change-queue-tester</h3>
<pre> Key: OVIRT-1918
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra</pre>
<p>Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3tuiUfRTk64K-2BOjFqOXf-2Fp-2B-2FjZcNAKKI5H7wrPtA-2FmirfW8Ytpa5TQyv2GiUXRx4WoV1mB617s0MIBVOnAceydFtelvzHyrvXpQeRGg8KMpBIGMmuA-2Fynjz5uTbLzLV3oQzOZ1F6YgeMieZbt9IrTvwRGLkBkyKcOl3A7gj-2BzcHqO2OGFg8TLi86Mrwv6SIE5n5VxidORzzPzG7nf95rBSxnChY-2B4BnC-2FpmgVlpi1RZPw6z-2Bpu-2Bin1x2jDRXrMwuTSdFbtFcbt-2BZgviBHVfUrOsjygqY7TCyCZdRNDTkaqh-2FBI-2FeK8-2BjYW6foewdR1RjpkFoEkBrv1ArcJERsmLcUF4NZslgSRHbpqh1JZ3BJmSSlGGK8h9MtCP5eCnwlnBQwaBVCLAf9-2FwoWpjqbIXGMFw68RuBSvwRHZ4EQ" 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>