Koji side tag as external repo?

[Iñaki Ucar]

Hi,

Is there any way to expose a Koji side tag as an external repo for
Copr? This would be useful to start a rebuild for rawhide before the
side tag is merged without having to set up a temporary Copr repo just
to rebuild that side tag.

Regards,
-- 
Iñaki Úcar

[Miro Hrončok]

On 14. 06. 20 13:56, Iñaki Ucar wrote:
>  Hi,
>  
>  Is there any way to expose a Koji side tag as an external repo for
>  Copr? This would be useful to start a rebuild for rawhide before the
>  side tag is merged without having to set up a temporary Copr repo just
>  to rebuild that side tag. 
Yes, for example:

https://kojipkgs.fedoraproject.org/repos/f33-boost/latest/$basearch


-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[Iñaki Ucar]

On Sun, 14 Jun 2020 at 19:03, Miro Hrončok <mhroncok(a)redhat.com&gt; wrote:
>  On 14. 06. 20 13:56, Iñaki Ucar wrote:
>  > Hi,
>  >
>  > Is there any way to expose a Koji side tag as an external repo for
>  > Copr? This would be useful to start a rebuild for rawhide before the
>  > side tag is merged without having to set up a temporary Copr repo just
>  > to rebuild that side tag.
>
>  Yes, for example:
>
>  https://kojipkgs.fedoraproject.org/repos/f33-boost/latest/$basearch 
That's what I was looking for, thanks. Is this documented somewhere?

-- 
Iñaki Úcar

[Kevin Fenzi]

On Sun, Jun 14, 2020 at 10:11:41PM +0200, Iñaki Ucar wrote:
>  On Sun, 14 Jun 2020 at 19:03, Miro Hrončok
> <mhroncok(a)redhat.com&gt; wrote:
>  >
>  > On 14. 06. 20 13:56, Iñaki Ucar wrote:
>  > > Hi,
>  > >
>  > > Is there any way to expose a Koji side tag as an external repo for
>  > > Copr? This would be useful to start a rebuild for rawhide before the
>  > > side tag is merged without having to set up a temporary Copr repo just
>  > > to rebuild that side tag.
>  >
>  > Yes, for example:
>  >
>  > https://kojipkgs.fedoraproject.org/repos/f33-boost/latest/$basearch
>  
>  That's what I was looking for, thanks. Is this documented somewhere? 
But note: 

* The repo could go away at any point once the builds are merged back

and

* If there's too much traffic and it causes problems, external repo
users may get blocked. ;) 

I don't know that we want to document this anywhere and ask more people
to use it...but we could put it somewhere (where I am not sure).

kevin

[Pavel Raiskup]

On Monday, June 15, 2020 1:10:42 AM CEST Kevin Fenzi wrote:
>  * If there's too much traffic and it causes problems, external
> repo
>  users may get blocked. ;)  
.. and Copr falls into the "external repo users" category (I am just not sure
this is well known fact).

Pavel

[Iñaki Ucar]

On Mon, 15 Jun 2020 at 01:10, Kevin Fenzi <kevin(a)scrye.com&gt; wrote:
>  On Sun, Jun 14, 2020 at 10:11:41PM +0200, Iñaki Ucar wrote:
>  > On Sun, 14 Jun 2020 at 19:03, Miro Hrončok <mhroncok(a)redhat.com&gt; wrote:
>  > >
>  > > On 14. 06. 20 13:56, Iñaki Ucar wrote:
>  > > > Hi,
>  > > >
>  > > > Is there any way to expose a Koji side tag as an external repo for
>  > > > Copr? This would be useful to start a rebuild for rawhide before the
>  > > > side tag is merged without having to set up a temporary Copr repo just
>  > > > to rebuild that side tag.
>  > >
>  > > Yes, for example:
>  > >
>  > > https://kojipkgs.fedoraproject.org/repos/f33-boost/latest/$basearch
>  >
>  > That's what I was looking for, thanks. Is this documented somewhere?
>
>  But note:
>
>  * The repo could go away at any point once the builds are merged back 
Then those builds are available in rawhide, so no problem.

>  * If there's too much traffic and it causes problems, external
> repo
>  users may get blocked. ;) 
Noted. I need to rebuild 14k packages for R 4.0. I hope I'm not causing trouble.

To avoid this for the use case I'm describing, Copr could have a
"create repo from koji tag" button that simply downloads the artifacts
from Koji and publishes a repo with those builds.

-- 
Iñaki Úcar

[Miro Hrončok]

On 15. 06. 20 10:10, Iñaki Ucar wrote:
> > * If there's too much traffic and it causes problems,
> external repo
> > users may get blocked.;)
>  Noted. I need to rebuild 14k packages for R 4.0. I hope I'm not causing trouble.
We have used the f33-python repo in the Python 3.9 copr when the side tag was 
"open". That was for about 5000 builds I guess. It was not blocked.

We also generally use the "Koji repo" for rawhide (served from the same 
location) with posibly hundreds thousand builds, where other people use that in 
Copr as well. I guess the main thing that helps is that Copr itself only runs a 
small integer of such builds at the same time.

>  To avoid this for the use case I'm describing, Copr could have a
>  "create repo from koji tag" button that simply downloads the artifacts
>  from Koji and publishes a repo with those builds. 
That only makes sense if the repo is not changing any more, right?

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[Iñaki Ucar]

On Mon, 15 Jun 2020 at 10:26, Miro Hrončok <mhroncok(a)redhat.com&gt; wrote:
>  On 15. 06. 20 10:10, Iñaki Ucar wrote:
>
>  > To avoid this for the use case I'm describing, Copr could have a
>  > "create repo from koji tag" button that simply downloads the artifacts
>  > from Koji and publishes a repo with those builds.
>
>  That only makes sense if the repo is not changing any more, right? 
Or if you just need a subset of packages for your builds that is already there.

-- 
Iñaki Úcar

[Kevin Fenzi]

On Mon, Jun 15, 2020 at 08:54:52AM +0200, Pavel Raiskup wrote:
>  On Monday, June 15, 2020 1:10:42 AM CEST Kevin Fenzi wrote:
>  > * If there's too much traffic and it causes problems, external repo
>  > users may get blocked. ;) 
>  
>  .. and Copr falls into the "external repo users" category (I am just not sure
>  this is well known fact). 
As far as I know things are fine now... I just would prefer not to make
it a repo on every fedora machine, etc... 

kevin