Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec>
CUSTOM_REPOS: You can add multiple Jenkins build urls/Yum repos, one per line. Supported formats are: * Jenkins Build url: e.g., http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/ * Yum repo: "rec:yum_repo_url" e.g., rec: http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/artifact/ It seems that this should work: 1. build sanlock rpms from my sanlock tree 2. copy to some public web server 3. create yum repo 4. add rec:http://my.server/sanlock-repo/ OST will pull sanlock from this repo, right? The biggest issue seems to be a public web server, I don't have one. Do we have something that I can use in jenkins.ovirt.org or other domain we control? I want to run these tests regularly, to make sure that sanlock always works with vdsm, without manual testing. Nir
_______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/RQFPBJBDCZKEZ2ES7HMF2XH6ZOIQV7MZ/
