[Mesa-dev] [PATCH v2 4/5] gitlab-ci: update base + llvm images with scheduled pipelines

Eric Anholt eric at anholt.net
Fri Sep 21 19:42:29 UTC 2018

"Juan A. Suarez Romero" <jasuarez at igalia.com> writes:

> On Thu, 2018-09-20 at 16:53 -0700, Eric Anholt wrote:
>> "Juan A. Suarez Romero" <jasuarez at igalia.com> writes:
>> > On Tue, 2018-09-04 at 08:19 -0700, Eric Anholt wrote:
>> > > "Juan A. Suarez Romero" <jasuarez at igalia.com> writes:
>> > > 
>> > > > Use scheduled pipelines to update both the base and the LLVM images.
>> > > > 
>> > > > This way allows to have an updated version of the base images even when
>> > > > the respect Rockerfiles keep the same.
>> > > 
>> > > I'm curious: does the scheduled build end up only updating the image
>> > > used by the normal CI path if the scheduled build passed tests?
>> > 
>> > Yes, it only updates the base + llvm base images; it does not execute any other
>> > task.
>> That sounds like you're actually saying "no" -- the scheduled build
>> would upload a new image, even if the new image with updated packages
>> can't build Mesa any more.
> Ah, yes, you're right. It only updates the base images, it doesn't try to check
> if Mesa builds or not. As it only updates the packages, and we are using an LTS
> distro in the base, hopefully it shouldn't break the build too many times. And
> if this happens, next push in Mesa will expose the problem.
> We have been using approach for several months in our side, and so far we never
> had this situation. But yes, could happen.

OK, if it's LTS I'm a lot less worried, though at that point it feels a
little silly to even bother.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180921/320ebbe0/attachment-0001.sig>

More information about the mesa-dev mailing list