<div dir="ltr">Already had one for master:<div><a href="http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64_build_from_patch/">http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64_build_from_patch/</a><br></div><div><br></div><div>Also,</div><div>there is the 'build any manual jobs' which were added to support official builds, see [1] for info, so you can also use them by providing a tarball, but I don't see an engine job for it.</div><div>Sandro, I guess you're not using the manual job to build official ovirt-engine builds?</div><div><br></div><div><br></div><div>[1] <a href="http://infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html#build-artifacts-manual-sh">http://infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html#build-artifacts-manual-sh</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 27, 2016 at 8:19 PM, Martin Mucha <span dir="ltr"><<a href="mailto:mmucha@redhat.com" target="_blank">mmucha@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you very much!<br>
<div class="HOEnZb"><div class="h5">M.<br>
<br>
----- Original Message -----<br>
> The options are combination of the distro and branch, I added the<br>
> job[1](el7, 4.0), to use it press 'build' from Jenkins's GUI and fill<br>
> in the GERRIT_REFSPEC to the needed patch.<br>
> As the build-artifacts job run on the limited resources of bare metal<br>
> hypervisors I restricted it for now to one concurrent job.<br>
><br>
> On infra side, I guess this can be yamlized later if it becomes<br>
> useful(just copy-paste of the current build-artifacts removing some<br>
> stages).<br>
><br>
><br>
> [1]<br>
> <a href="http://jenkins.ovirt.org/job/ovirt-engine_4.0_build-artifacts-el7-x86_64-manual/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>ovirt-engine_4.0_build-<wbr>artifacts-el7-x86_64-manual/</a><br>
><br>
><br>
> On Thu, Oct 27, 2016 at 3:18 PM, Dan Kenigsberg <<a href="mailto:danken@redhat.com">danken@redhat.com</a>> wrote:<br>
> > On Thu, Oct 27, 2016 at 06:32:47AM -0400, Martin Mucha wrote:<br>
> >> Hi,<br>
> >><br>
> >> let me step back a little and explain what we want to achieve. We have<br>
> >> patch pushed to gerrit, not merged to master. We want to build rpms from<br>
> >> it and pass it (via no official way) to some tester so that he can test<br>
> >> it.<br>
> >><br>
> >> I read provided documentation, but I do not have sufficient background to<br>
> >> understand it fully.<br>
> >> Questions:<br>
> >><br>
> >> 1. if I opted to run these tests locally, what are expected hw<br>
> >> specification? I mean devel build is already more than laptop can handle.<br>
> >> If this has enabled all translations, I'd have to take a pto to run it.<br>
> >> So is this even possible to be ran on laptop with only 12G ram?<br>
> >><br>
> >> 2. Since I probably should be coding instead of waiting for build on<br>
> >> irresponsible laptop (which it is even for devel build), would it be<br>
> >> possible to have jenkins build, which prepares rpms as described above<br>
> >> without need to deploy them to some repo, but allowing to download them<br>
> >> instead?<br>
> >><br>
> >> thanks,<br>
> >> M.<br>
> >><br>
> >> ----- Original Message -----<br>
> >> > Hi,<br>
> >> > first you can run it locally quite easily using mock[1], the command<br>
> >> > should be(after jenkins repo is cloned and mock installed) something<br>
> >> > like:<br>
> >> > ../jenkins/mock_configs/mock_<wbr>runner.sh --mock-confs-dir<br>
> >> > ../jenkins/mock_configs/ --build-only -s fc24<br>
> >> > After running successfully the artifacts will be under<br>
> >> > exported-artifacts directory.<br>
> >> ><br>
> >> > It is possible to do it from Jenkins too, the problem is that the<br>
> >> > current _build_artifacts job also deploy the created RPMs to<br>
> >> > <a href="http://resources.ovirt.org" rel="noreferrer" target="_blank">resources.ovirt.org</a>'s experimental repo, which is later consumed by<br>
> >> > OST.<br>
> >> > If needed, we can clone the needed job and remove the deploy part(and<br>
> >> > add -manual suffix), then you can pass the gerrit refspec in the build<br>
> >> > parameters. If so, tell me which job.<br>
> ><br>
> > Adding to Matin's explaination: He posted <a href="https://gerrit.ovirt.org/65793" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/65793</a><br>
> > and would like it be tested. It would be wonderful if you can add a job<br>
> > that makes it possible to build el7 rpms from that patch, to bet<br>
> > executed by QE.<br>
> ><br>
> > So yes, I'd appreciate if you can add such a -manual job for building<br>
> > ovirt-engine. I'm not sure I know "which job" precisely is that, though.<br>
> > Can you tell me which are the options?<br>
> ><br>
> > Regrards,<br>
> > Dan.<br>
><br>
______________________________<wbr>_________________<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/<wbr>mailman/listinfo/infra</a><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV 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></div>
</div>