On Thu, 18 Jul 2024 at 08:19, Pavel Raiskup wrote:
> Indeed. Plus, per-package, you can set the max number of builds that
> are being kept.
>
AFAIK, the max number of builds option applies to *any* build, successful
or not. This is not useful, and I think I opened an RFE at some point. For
me,
Pavel Raiskup wrote:
> Yes, I believe there are high chances to accept this (much harder will
> to prioritize the feature). If you know what you are doing, the point
> should not be to make the prolonging process click-expensive - which it
> admittedly is now, if you maintain dozens of long-term p
On čtvrtek 18. července 2024 3:48:30, SELČ Kevin Kofler via devel wrote:
> Pavel Raiskup wrote:
> > Have you considered to submit an RFE for this "Extend All" feature?
> > I think this convenience button (or even with API, if reasonably easy to
> > implement) sounds like an acceptable compromise to
On středa 17. července 2024 11:21:15, SELČ David Bold wrote:
> Adam Samalik wrote:
> > On Wed, 17 Jul 2024 at 10:54, Pavel Raiskup prais...@redhat.com wrote:
> > > On úterý 16. července 2024 15:22:56, SELČ Stephen Gallagher wrote:
> > > On Tue, Jul 16, 2024 at 3:44 AM Pavel Raiskup prais...@redhat.
Pavel Raiskup wrote:
> Have you considered to submit an RFE for this "Extend All" feature?
> I think this convenience button (or even with API, if reasonably easy to
> implement) sounds like an acceptable compromise to me.
I remember having once suggested that on this mailing list and having
rece
Adam Samalik wrote:
> On Wed, 17 Jul 2024 at 10:54, Pavel Raiskup prais...@redhat.com wrote:
> > On úterý 16. července 2024 15:22:56, SELČ Stephen Gallagher wrote:
> > On Tue, Jul 16, 2024 at 3:44 AM Pavel Raiskup prais...@redhat.com
> > wrote:
> > [snip]
> > Do you suggest moving rawhide to branch
On Wed, 17 Jul 2024 at 10:54, Pavel Raiskup wrote:
> On úterý 16. července 2024 15:22:56, SELČ Stephen Gallagher wrote:
> > On Tue, Jul 16, 2024 at 3:44 AM Pavel Raiskup
> wrote:
> >
> > [snip]
> >
> > > Do you suggest moving rawhide to branched, and start with a fresh
> (empty)
> > > rawhide ch
On úterý 16. července 2024 15:22:56, SELČ Stephen Gallagher wrote:
> On Tue, Jul 16, 2024 at 3:44 AM Pavel Raiskup wrote:
>
> [snip]
>
> > Do you suggest moving rawhide to branched, and start with a fresh (empty)
> > rawhide chroots for every branching?
>
> Yes, that was exactly what I was sugges
On Tue, Jul 16, 2024 at 3:44 AM Pavel Raiskup wrote:
>
> On pondělí 15. července 2024 16:32:45, SELČ Stephen Gallagher wrote:
> > On Mon, Jul 15, 2024 at 10:21 AM Miroslav Suchý wrote:
> > >
> > > Dne 15. 07. 24 v 2:57 odp. Stephen Gallagher napsal(a):
> > >
> > > Instead of always keeping "Rawhi
Thank you for the reply, Kevin.
On úterý 16. července 2024 3:34:06, SELČ Kevin Kofler via devel wrote:
> Pavel Raiskup wrote:
> > This is a gentle heads-up (at least a year in advance) that we plan to
> > address Fedora Copr storage consumption related to Fedora Rawhide
> > builds. Currently, Raw
On pondělí 15. července 2024 16:32:45, SELČ Stephen Gallagher wrote:
> On Mon, Jul 15, 2024 at 10:21 AM Miroslav Suchý wrote:
> >
> > Dne 15. 07. 24 v 2:57 odp. Stephen Gallagher napsal(a):
> >
> > Instead of always keeping "Rawhide" around as a separate buildroot,
> > why not just rename it at Br
Dne 16. 07. 24 v 3:34 dop. Kevin Kofler via devel napsal(a):
The real issue still appears to be that "Disk storage is the commodity that
incurs the highest cloud costs.", which means that cloud might not be the
right technology to use here. Or at least the particular cloud
implementation you are
On pondělí 15. července 2024 12:10:58, SELČ Sandro via devel wrote:
> On 15-07-2024 10:24, Pavel Raiskup wrote:
> > TL;DR: We plan to start monitoring build activity in Copr projects.
> > If no builds appear for a long time in these "rolling" chroots (such as
> > Fedora Rawhide), we'll disable such
Pavel Raiskup wrote:
> This is a gentle heads-up (at least a year in advance) that we plan to
> address Fedora Copr storage consumption related to Fedora Rawhide
> builds. Currently, Rawhide build results are kept indefinitely, but
> this is going to change in the future.
>
> For the full story,
On Mon, Jul 15, 2024 at 10:21 AM Miroslav Suchý wrote:
>
> Dne 15. 07. 24 v 2:57 odp. Stephen Gallagher napsal(a):
>
> Instead of always keeping "Rawhide" around as a separate buildroot,
> why not just rename it at Branching and then create a NEW Rawhide
> chroot?
>
> 1) Different workflow compare
Dne 15. 07. 24 v 2:57 odp. Stephen Gallagher napsal(a):
Instead of always keeping "Rawhide" around as a separate buildroot,
why not just rename it at Branching and then create a NEW Rawhide
chroot?
1) Different workflow compared to the one we have in Fedora.
2) Create it with what? Empty conte
On Mon, Jul 15, 2024 at 4:25 AM Pavel Raiskup wrote:
>
> Hello maintainers.
>
> This is a gentle heads-up (at least a year in advance) that we plan to
> address Fedora Copr storage consumption related to Fedora Rawhide
> builds. Currently, Rawhide build results are kept indefinitely, but
> this i
On 15-07-2024 10:24, Pavel Raiskup wrote:
TL;DR: We plan to start monitoring build activity in Copr projects.
If no builds appear for a long time in these "rolling" chroots (such as
Fedora Rawhide), we'll disable such chroots, preserve the built results
for a while, and then delete them if no act
Hello maintainers.
This is a gentle heads-up (at least a year in advance) that we plan to
address Fedora Copr storage consumption related to Fedora Rawhide
builds. Currently, Rawhide build results are kept indefinitely, but
this is going to change in the future.
For the full story, see the blog
19 matches
Mail list logo
