[ovirt-devel] Re: Deprecating direct RPM downloads from Jenkins

On 19 June 2018 at 17:37, Michal Skrivanek <michal.skrivanek(a)redhat.com&gt; wrote: > > > On 19 Jun 2018, at 07:16, Barak Korren <bkorren(a)redhat.com&gt; wrote: > > Hi there, > > > TL;DR: Is your build/CI/other process consuming RPMs directly from > Jenkins? Could it be changed to consume from other available places? > > >

> In STDCI V1 we supported obtaining of the latest CI build for a > particular project in a particular branch on a particular platform directly > from Jenkins, by using the "latestSuccessfulBuild" dynamic link that > Jenkins generates. > > This was possible in STDCI V1 because we had one-to-one correlation > between jenkins jobs and project/branch/platform combinations. That is no > longer the case in STDCI V2 where each project gets just two fixed jobs > that adjust themselves automatically to run needed functionality. > > We could implement some equivalent functionality in STDCI V2 by for e.g. > uploading builds to some predictable locations on an artifact server, but > that will take some non-trivial amount of work, so it leads us to the > question if this functionality is really needed. > > > does this affect the repo/rpms created as part of a “ci please build” run > in any way? > The URL for the RPM will be different but as long as you use the full job/build URL it will work. In short, no. This only affects you if you need some kind of a 'meta' URL to find the build from the lastest _merged_ commit. > > > There are a couple of alternatives locations to get recently built > packages from: > - The 'tested' repo which contains all the packages that passed CQ/OST > - The 'snapshot' repo which contains a nightly snapshot of 'tested'. > > So given the options above, if you have a build/CI/other process that > currently consumes builds from Jenkins, could it be changed to consume from > the other available locations? > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > 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/devel@ovirt.org/message/A5LFDPPFWXT... > > > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org 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/devel@ovirt.org/message/GX6GRYIVJ2W...