DevHeads.net

Batched updates for development cycles

Hi All,

It seems batched updates is turned on for F-27 [1], surely it makes
sense for updates to go straight out in the development cycle, this
affects things getting into the nightly composes for testing in live
images and other such things.

I feel this should be something that is only used for stable releases.

[1] <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f40de8609" title="https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f40de8609">https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f40de8609</a>

Comments

Re: Batched updates for development cycles

By Randy Barlow at 10/15/2017 - 13:01

I filed an issue to request this change:

<a href="https://github.com/fedora-infra/bodhi/issues/1895" title="https://github.com/fedora-infra/bodhi/issues/1895">https://github.com/fedora-infra/bodhi/issues/1895</a>

Re: Batched updates for development cycles

By Randy Barlow at 10/14/2017 - 11:11

On 10/12/2017 03:06 AM, Peter Robinson wrote:
Hey Peter!

Since branched releases have the updates-testing repository enabled by
default, won't the effect you desire happen anyway?

I'm not opposed to modifying the system so that it doesn't batch for
stable releases, but I'm curious why the default updates-testing repo
doesn't satisfy the need.

Re: Batched updates for development cycles

By Peter Robinson at 10/14/2017 - 11:45

On Sat, Oct 14, 2017 at 5:11 PM, Randy Barlow
< ... at fedoraproject dot org> wrote:
No, because the updates-testing repo is enabled by default for
installs, it's not enabled for the composes so things like Live, ARM
and cloud images when composed don't include the contents of
updates-testing. If you updated them once they are booted they pull in
testing, but the pungi compose that generates them only consumes the
f27 tag.

You're confusing stable releases (F25 and F26) vs development/branched
releases (F27) and see above for the answer to that. IMO the stable
releases should have batched updates, the branched releases either
shouldn't or if they do the 'batches' should be sent out daily.

Re: Batched updates for development cycles

By Randy Barlow at 10/14/2017 - 17:14

On 10/14/2017 12:45 PM, Peter Robinson wrote:
Ah, that makes sense. Do composes happen every day for branched, or are
they special events? I ask because the way Bodhi moves updates from
batched to stable is by running a very simple CLI (via cron). If the
composes are special non-daily events, maybe releng could simply run
that script when they want to make a compose. If they are daily events,
I think we'll need to patch Bodhi so that it skips the batched thing for
branched releases.

Sorry, I meant to say "branched" instead of "stable", and actually that
second paragraph was redundant with my first one and I could have just
left it off ☺

Re: Batched updates for development cycles

By Peter Robinson at 10/15/2017 - 03:07

On Sat, Oct 14, 2017 at 11:14 PM, Randy Barlow
< ... at fedoraproject dot org> wrote:
Daily run by cron job, only composes that are special events are
release candidates.

;-)

Re: Batched updates for development cycles

By Zbigniew =?utf-... at 10/12/2017 - 02:12

On Thu, Oct 12, 2017 at 08:06:18AM +0100, Peter Robinson wrote:
... or we could make the batches go out daily to still test the
batching mechanism as far as possible without actually delaying
anything.

Zbyszek

Re: Batched updates for development cycles

By Matthew Miller at 10/12/2017 - 08:59

On Thu, Oct 12, 2017 at 07:12:51AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
Ooh, that's a good idea. +1.

Re: Batched updates for development cycles

By Peter Robinson at 10/12/2017 - 02:38

On Thu, Oct 12, 2017 at 8:12 AM, Zbigniew Jędrzejewski-Szmek
< ... at in dot waw.pl> wrote:
Sure, I don't care what the implementation details are.....