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 <[email protected]> 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 > [email protected] > http://lists.ovirt.org/mailman/listinfo/infra _______________________________________________ Infra mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/infra
