Note: moving the build part to mock might not be as easy as I initially thought because IIRC the engine build_artifacts.sh script builds all GWT permutations which are hardly needed for this job. We might need to commit some stand-alone quick build script to the engine repo, and that may take some time.

So if the above is true, just moving to the experimental flow might be a faster approach.

can we move the build part to mock to get rid of this dependencies on hosts?

Thanks for following up on this - this still has to be puppetized as we've been adding el7 slaves recently and these packages may end up missing.

Here's the list of packages I installed via fabric:
hystrix-core archaius-core rxjava jctools hystrix-metrics-event-stream

Can't recall where I got this list of packages (likely from some job definition) but I'll add them as a new class like "ovirt_jenkins_slave::engine_builder" if you don't mind. Another option, as proposed by Barak, is to change the job to build inside mock and install the package there instead - sounds much better to me but I'm not that familiar with Jenkins jobs and will need some help if we go that way.

is there an action item on this via puppet or we can close it?

was this resolved or we are still waiting to add it to puppet?

please close this ticket or convert it to adding this as puppet code.

As a quick and dirty test I installed the RPM using a fabric task to EL7 VMs and now monitoring the latest build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merged/398/console
It doesn't seem to fail immediately after trying to build the RPM so I assume we're good and the build is happening.

If it is indeed a missing build dep (not sure hysterix should really be needed during the build process), then maybe the best way to deal with this once and for all is just to run the build part of the job inside mock.
(A quick hack to do this would be to copy the building part of check_patch.sh to a temporary script and run it with mock_runner.sh. A more stable solution would be to then submit the temp script is a patch to engine. We can also use build_articafts.sh but I think that does a slow full-permutation build)

this looks like the right theory as I don't see any "yum install" steps in the console output and the create_rpms function is just an rpmbuild:
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/ovirt-engine_upgrade_to_4.0/build_engine_rpm.sh;h=abf29b8c5e7450fe3a80ff641965943b99349de3;hb=refs/heads/master#l131

So indeed it looks like this line with build dependencies has to be updated with hystrix:
https://gerrit.ovirt.org/gitweb?p=infra-puppet.git;a=blob;f=site/ovirt_jenkins_slave/manifests/engine_test_runner.pp;h=e58213088da05a0f8e1d2993db42f9c1a728f5c3;hb=refs/heads/production#l53

Might be as this is a none standard-ci job, it assumes the packages are already installed, if this is indeed the case, it is controlled by:
infra-puppet.git/site/ovirt_jenkins_slave/manifests/engine_test_runner.pp
adding it to there will cause the hystrix packages to be installed on all slaves.. wonder if we can avoid that though..