building engine artificats from a posted patch?

[Roy Golan]

On 27 October 2016 at 13:32, Martin Mucha <mmucha at redhat.com> 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 from it
> and pass it (via no official way) to some tester so that he can test it.
>
> I read provided documentation, but I do not have sufficient background to
> 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 handle.
> If this has enabled all translations, I'd have to take a pto to run it. So
> is this even possible to be ran on laptop with only 12G ram?
>
> PTO isn't needed if your tester doesn't need all locales + permutations


> 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 them
> instead?
>
>
You can already explore the CI jenkins jobs on how to do it or have a look
at this jenkins job
http://jenkins-dev.eng.lab.tlv.redhat.com/job/ovirt-engine-create-rpms/


> thanks,
> M.
>
> ----- Original Message -----
> > Hi,
> > first you can run it locally quite easily using mock[1], 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 by
> > OST.
> > If needed, we can clone the needed job and remove the deploy part(and
> > add -manual suffix), then you can pass the gerrit refspec in the build
> > parameters. If so, tell me which job.
> >
> > Nadav.
> >
> >
> > [1]
> > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/
> Build_and_test_standards.html#testing-the-scripts-locally
> >
> > On Wed, Oct 26, 2016 at 5:47 PM, Dan Kenigsberg <danken at redhat.com>
> wrote:
> > > Hi,
> > >
> > > Pardon my ignorance, but how can I trigger build-artifacts.sh after
> > > posting a patch to gerrit?
> > >
> > > I hope there's an easy way togenerate RPMs to be tested by third
> > > parties prior to merging the patch.
> > >
> > > Regards,
> > > Dan.
> > > _______________________________________________
> > > Infra mailing list
> > > Infra at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/infra
> >
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20161027/7e17881c/attachment.html>