On Sun, May 19, 2019 at 8:43 AM Barak Korren <bkorren@redhat.com> wrote:

On Sun, 19 May 2019 at 00:01, Nir Soffer <nsoffer@redhat.com> wrote:

Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build

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 doesn't actually have to be a yum repo, 'rec:' simply does a recursive HTTP crawl.

`repoman` and therefore OST does not actually support reading YUM metadata ATM.

Thanks, testing with latest build now:

rec:https://cbs.centos.org/kojifiles/packages/sanlock/3.7.3/1.el7/x86_64/

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4764/

  

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

no need for that, but the web server needs to be browsable.

 

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?

To be in jenkinsit needs to be build by jenkins...

 

I want to run these tests regularly, to make sure that sanlock always works with vdsm, without manual

testing.

I think there are couple of solutions here you could consider:

1. Setup a build repo containing automation files for oVirt and have oVirt's CI system run the builds. this will enable full automation for the whole test process

Do you mean project without any source, only stdci.yaml and build script

pulling sanlock source from master, and creating rpms? 

Can we use my sanlock fork on github for this?
https://github.com/nirs/sanlock

1. Build via copr - in which case copt will provide HTTP hosting for the resulting RPMs.

Interesting, but I think I need cbs instead, since we don't have Fedora OST yet.

I think the simplest way would something like fedpkg scratch build use the build URL.

Sandro, what do I need to be able to do scratch builds in cbs?

https://cbs.centos.org/koji/index