[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

> On Nov 16, 2018, at 3:41 PM, Dario Faggioli <dfaggioli@xxxxxxxx> wrote:
>> On Fri, 2018-11-16 at 19:50 +0100, Dario Faggioli wrote:
>>> On Fri, 2018-11-16 at 18:44 +0000, Wei Liu wrote:
>>>> On Fri, Nov 16, 2018 at 07:30:55PM +0100, Dario Faggioli wrote:
>>> I have been playing with the CI system today so it could have been
>>> a
>>> bit
>>> overwhelmed. Let's wait until next week to see if it comes back.
>> Ok, sure. What I'm most interested, is to see if the opensuse jobs
>> pass
>> (i.e., if I got the rune, the name of the container, etc, right :-)
>> ).
> And... it worked! :-)
> Now, the next step would be to add openSUSE Tumbleweed too.
> 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. We could create a pipeline to rebuild containers 
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.