Skip to content

CI: default:artifacts:expire_in is ignored

Summary

When the expire_in value is defined in the default section, this is ignored by gitlab ci.

Steps to reproduce

Define a .gitlab-ci.yml like this and trigger the pipeline (see example project)

default:
  artifacts:
    expire_in: 1 day

stages:
  - expire

expire:default:
  image: galilee/php-tester:7.3
  stage: expire
  cache:
    paths:
      - .composer
  script:
    - composer install --prefer-dist --no-progress
  artifacts:
    paths:
      - vendor

expire:specific:
  image: galilee/node-build:12
  stage: expire
  cache:
    paths:
      - .npm
  script:
    - npm ci
  artifacts:
    paths:
      - node_modules
    expire_in: 12 hours

Example Project

https://gitlab.com/s7b4/gitlab-bugreport

What is the current bug behavior?

artifacts for expire:default job never expires (instance wide setting)

artifacts for expire:specific job expires in 12h (as defined in gitlab-ci.yml)

What is the expected correct behavior?

artifacts for expire:default expires in 1d.

Relevant logs and/or screenshots

expire:default

Capture_d_écran_du_2020-05-01_10-08-40

expire:specific

Capture_d_écran_du_2020-05-01_10-08-21

Output of checks

This bug happens on GitLab.com

Regards.

Edited by Jason Yavorsky