> 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 w
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
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
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
