[ https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jir... ] eyal edri commented on OVIRT-1602: ---------------------------------- [~didi(a)redhat.com] just fyi, the current manual job supports running on any projects you want, just list them one on each line. something that will be more challengin to do if you start specifying gerrit links. The ideal solution will be to indeed enable patch gating, but it might take some time to enable, so its not feasable in the near future. We still need to think if its possible to support something else which won't hurt our system integrity, we are working hard to make the Jenkins system more scalable and maintainable, and we can only do that by sticking to the architecture we designed as part of "std-ci". Implemeting a hacky solution outside of the std-ci umbrella will bring us back to weird jenkins jobs and scripts that are hard to debug and maintain going forward. You can try perhaps writing a local script to do it for you, something like : 1. run 'build-artifacts.sh' ( or build-on-demand ) locally via mock runner for each of the projects you want to build from and save the RPMs to local repo 2. run the suite you want from ost repo, providing links to the local repos using the '-s' option. [1] [1] http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/ -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)