Mailinglist Archive: opensuse-buildservice (65 mails)
< Previous | Next > |
Re: [opensuse-buildservice] Container rebuild trigger on included packages and registry multiple tags
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Fri, 14 Sep 2018 09:19:46 +0200
- Message-id: <2644220.qzvBhfNiVy@linux-izwb.site>
On Freitag, 14. September 2018, 01:19:00 CEST wrote Jimmy Berry:
right, it is a low prio event. So it can take some time, but it is the default
setting.
not atm, but this is in first place a limitation of kiwi.
However, we have a feature open to add further tags independend of the build
description
you can, but you need to go the maintenance approach then atm. means, creating
a new package container for each build you want to keep.
Hey, no bad mood on friday morning!
--
Adrian Schroeter
email: adrian@xxxxxxx
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx
On Thursday, August 30, 2018 10:34:09 PM CDT Jimmy Berry wrote:
Two questions:
- Is it possible to have a container rebuild whenever the underlying
packages are updated (ie. any package included in the container) even if
the packages are in underlying repo path elements and not the project with
the container?
This seems to occur somewhat frequently, but not immediately after package
updates.
right, it is a low prio event. So it can take some time, but it is the default
setting.
- Is it possible to publish multiple tags to the opensues registry? Using
additionaltags on containerconfig element in kiwi file they are supposedly
set, but only tag ends up in the registry.
not atm, but this is in first place a limitation of kiwi.
However, we have a feature open to add further tags independend of the build
description
- Related is it possible to keep older revisions (a couple) or "pin" certain
tags and keep those until unpinned? Having only a single version of a
container is not ideal as it makes it impossible to roll-back to previous
version.
you can, but you need to go the maintenance approach then atm. means, creating
a new package container for each build you want to keep.
:(
Hey, no bad mood on friday morning!
--
Adrian Schroeter
email: adrian@xxxxxxx
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx
< Previous | Next > |