Re: [PATCH 0/2] automation: build in an openSUSE Leap container.

From: Wei Liu <wei.liu2@citrix.com>
To: Dario Faggioli <dfaggioli@suse.com>
Cc: xen-devel@lists.xenproject.org,
	Doug Goldstein <cardoe@cardoe.com>, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH 0/2] automation: build in an openSUSE Leap container.
Date: Sat, 17 Nov 2018 10:37:02 +0000	[thread overview]
Message-ID: <20181117103702.5votgjpr265igkji@zion.uk.xensource.com> (raw)
In-Reply-To: <99e079e2d8a7bb44b528cafb58f5daef474d7e82.camel@suse.com>

On Sat, Nov 17, 2018 at 12:07:28AM +0100, Dario Faggioli wrote:
> On Fri, 2018-11-16 at 16:51 -0600, Doug Goldstein wrote:
> > > On Nov 16, 2018, at 3:41 PM, Dario Faggioli <dfaggioli@suse.com>
> > > wrote:
> > > 
> > > But I have a question, Tumbleweed is rolling (and it's actually
> > > rolling
> > > quite fast); how can we handle that?
> > > 
> > > I'd say the container image should be rebuild (or, at least, the
> > > 'package refresh && package update' bits of the dockerfile be re-
> > > executed), if not at every run of the pipeline, frequently enough.
> > > Can
> > > we do that?
> > > 
> > > I see that we have Debian unstable, which is also rolling, but do
> > > we
> > > actually update it, or is it, basically, just a snapshot?
> > 
> > It’s basically a snapshot. 
> >
> Ok.
> 
> > We could create a pipeline to rebuild containers periodically. 
> >
> Right. If that's doable, then I'll just prepare another dockerfile for
> Tumbleweed (will be very similar to this one, although probably not
> identical... I'll see about sharing/consolidating, but can't promise).
> 
> And then we do the rebuilding pipeline trick, at least for the images
> of rolling distros.

We should do that for all distros, because even the stable ones do point
releases from time to time.

Your series is now pushed, BTW.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel