there is the 'build any manual jobs' which were added to support official
builds, see  for info, so you can also use them by providing a tarball,
but I don't see an engine job for it.
Sandro, I guess you're not using the manual job to build official
On Thu, Oct 27, 2016 at 8:19 PM, Martin Mucha <mmucha(a)redhat.com> wrote:
Thank you very much!
----- Original Message -----
> The options are combination of the distro and branch, I added the
> job(el7, 4.0), to use it press 'build' from Jenkins's GUI and fill
> in the GERRIT_REFSPEC to the needed patch.
> As the build-artifacts job run on the limited resources of bare metal
> hypervisors I restricted it for now to one concurrent job.
> On infra side, I guess this can be yamlized later if it becomes
> useful(just copy-paste of the current build-artifacts removing some
> On Thu, Oct 27, 2016 at 3:18 PM, Dan Kenigsberg <danken(a)redhat.com>
> > On Thu, Oct 27, 2016 at 06:32:47AM -0400, Martin Mucha wrote:
> >> Hi,
> >> let me step back a little and explain what we want to achieve. We have
> >> patch pushed to gerrit, not merged to master. We want to build rpms
> >> it and pass it (via no official way) to some tester so that he can
> >> it.
> >> I read provided documentation, but I do not have sufficient
> >> understand it fully.
> >> Questions:
> >> 1. if I opted to run these tests locally, what are expected hw
> >> specification? I mean devel build is already more than laptop can
> >> If this has enabled all translations, I'd have to take a pto to run
> >> So is this even possible to be ran on laptop with only 12G ram?
> >> 2. Since I probably should be coding instead of waiting for build on
> >> irresponsible laptop (which it is even for devel build), would it be
> >> possible to have jenkins build, which prepares rpms as described above
> >> without need to deploy them to some repo, but allowing to download
> >> instead?
> >> thanks,
> >> M.
> >> ----- Original Message -----
> >> > Hi,
> >> > first you can run it locally quite easily using mock, the command
> >> > should be(after jenkins repo is cloned and mock installed) something
> >> > like:
> >> > ../jenkins/mock_configs/mock_runner.sh --mock-confs-dir
> >> > ../jenkins/mock_configs/ --build-only -s fc24
> >> > After running successfully the artifacts will be under
> >> > exported-artifacts directory.
> >> >
> >> > It is possible to do it from Jenkins too, the problem is that the
> >> > current _build_artifacts job also deploy the created RPMs to
> >> > resources.ovirt.org's experimental repo, which is later consumed
> >> > OST.
> >> > If needed, we can clone the needed job and remove the deploy
> >> > add -manual suffix), then you can pass the gerrit refspec in the
> >> > parameters. If so, tell me which job.
> > Adding to Matin's explaination: He posted
> > and would like it be tested. It would be wonderful if you can add a job
> > that makes it possible to build el7 rpms from that patch, to bet
> > executed by QE.
> > So yes, I'd appreciate if you can add such a -manual job for building
> > ovirt-engine. I'm not sure I know "which job" precisely is that,
> > Can you tell me which are the options?
> > Regrards,
> > Dan.
Infra mailing list
EMEA ENG Virtualization R&D
Red Hat Israel
irc: eedri (on #tlv #rhev-dev #rhev-integ)