Re: Pop up from Gitlab about Job artifacts expiring

[Jonas Hahnfeld]

Hi James, all,

before that date last year (June 22, 2020) it was possible to create CI
artifacts that never expired. This posed problems (huge data volume)
for GitLab Inc running gitlab.com, so they decided to add an expiration
date retrospectively. I guess that some may start to expire around now
which could be unexpected if users relied on this 'never' happening.
However, LilyPond isn't affected by this, our artifacts expire after
one week (IIRC) and have been since the beginning.

Cheers
Jonas

Am Freitag, dem 15.01.2021 um 09:15 +0000 schrieb James:
> OK, I guess the inline attachments didn't work.
> 
> Sorry,
> 
> Here is the text verbatim.
> 
> --snip--
> 
> Important changes to default expiration dates for job meta data and 
> artifacts took effect on June 22, 2020. As part of this change 
> expiration dates have been applied to job artifacts that were created 
> without them. Find out more details and why this benefits all @gitlab 
> <https://gitlab.com/gitlab> users via our blog 
> <https://about.gitlab.com/blog/2020/06/18/job-artifact-meta-data-expiration-change/>.
> 
> --snip--
> 
> 
> On 15/01/2021 09:07, James wrote:
> > Hello,
> > 
> > I suddenly started getting this pop up when looking at reg tests from 
> > our CI system.
> > 
> > 
> > I can see the date is from last year, so I don't know the significance 
> > of me seeing this 'today' - after all, I've been looking at CI reg 
> > tests for a while now and not seen this before.
> > 
> > So in case this means something to someone or it matters, I thought 
> > I'd mention it.
> > 
> > James
> >

signature.asc
Description: This is a digitally signed message part