building engine artificats from a posted patch?
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.
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... On Wed, Oct 26, 2016 at 5:47 PM, Dan Kenigsberg <danken@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? 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? thanks, M. ----- Original Message -----
On 27 October 2016 at 13:32, Martin Mucha <mmucha@redhat.com> wrote:
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/
On Thu, Oct 27, 2016 at 1:32 PM, Martin Mucha <mmucha@redhat.com> wrote:
On a side note, you will need to make sure whoever you pass the RPMs to has the needed repositories with the dependencies(besides the created RPMs..), probably exploring OST dependencies, for example[1] will help. Nadav. [1] https://github.com/oVirt/ovirt-system-tests/blob/master/common/yum-repos/ovi... On Thu, Oct 27, 2016 at 1:54 PM, Roy Golan <rgolan@redhat.com> wrote:
On Thu, Oct 27, 2016 at 06:32:47AM -0400, Martin Mucha wrote:
Adding to Matin's explaination: He posted https://gerrit.ovirt.org/65793 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, though. Can you tell me which are the options? Regrards, Dan.
The options are combination of the distro and branch, I added the job[1](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 stages). [1] http://jenkins.ovirt.org/job/ovirt-engine_4.0_build-artifacts-el7-x86_64-man... On Thu, Oct 27, 2016 at 3:18 PM, Dan Kenigsberg <danken@redhat.com> wrote:
Already had one for master: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64_... Also, 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. Sandro, I guess you're not using the manual job to build official ovirt-engine builds? [1] http://infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html#... On Thu, Oct 27, 2016 at 8:19 PM, Martin Mucha <mmucha@redhat.com> wrote:
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
I finally got to trying to use those jobs: http://jenkins.ovirt.org/job/ovirt-engine_4.0_build-artifacts-el7-x86_64-man... or http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64_... and it seems, that I don't have privileges to run them. Can you please look at it? Also over time I lost privilege to re-trigger failed jenkins jobs, if this is something different, can you re-grant me privileges to do that? thanks, M. ----- Original Message -----
Also over time I lost privilege to re-trigger failed jenkins jobs, if this is something different, can you re-grant me privileges to do that?
Hi Martin, I granted you the 'edv' role on Jenkins. It should provide you wiht what you need. -- Barak Korren bkorren@redhat.com RHEV-CI Team
participants (6)
-
Barak Korren -
Dan Kenigsberg -
Eyal Edri -
Martin Mucha -
Nadav Goldin -
Roy Golan