<div dir="ltr">Actually there is a ticket [1] to remove all dao tests jobs and move them to STD CI,<div>But as Barak said the jobs can't run without a DB and postgres installed, so support should be added to the STD ci code (probably copying it and adjust from the current jobs?)</div><div><br></div><div>Example of existing dao tests job:</div><div><a href="http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_created/14952/consoleFull">http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_created/14952/consoleFull</a><br></div><div><br></div><div><br></div><div>[1] <a href="https://ovirt-jira.atlassian.net/browse/OVIRT-450">https://ovirt-jira.atlassian.net/browse/OVIRT-450</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 28, 2016 at 6:52 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 27 March 2016 at 20:57, Yevgeny Zaspitsky <<a href="mailto:yzaspits@redhat.com">yzaspits@redhat.com</a>> wrote:<br>
> Hi All,<br>
><br>
> I renamed NetworkAttachmentDaoTest.java to NetworkAttachmentDaoImplTest.java<br>
> (note the added "Impl") and Jenkins now includes the test in the regular<br>
> unit-tests run rather than running that as a dao-unit-tests job. That causes<br>
> test to fail as it cannot connect ot the tests DB.<br>
><br>
> Where the logic of choosing the right configuration sits?<br>
> Shouldn't any dal change trigger the dao tests rather than the regular ones?<br>
><br>
<br>
</span>I'm not sure which project are you referring to, but if you are<br>
talking about a project which uses Standard CI, then all the logic<br>
resides either in the scripts in the automation directory or in the<br>
tools they invoke.<br>
The only logic which does not sit there (for now) is which of the 3<br>
Std-CI stages to run for which OS.<br>
<br>
What this means WRT the above is that the logic to set up the test DB<br>
needs to be embedded in the automation script (probably<br>
check_patch.sh) as well as the logic to decide which patch to run.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
RHEV-CI Team<br>
_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div>