> 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.
It is, however, possible to avoid expiration. I've activated this for one pipeline https://lilypond.gitlab.io/-/lilypond/-/jobs/944871436/artifacts/test-results/index.html so that I have a demo example how the FreeType testing system should evolve :-) Werner
