Ability to require artifacts to exists and fail the job otherwise

Description

When job artifacts are not found job log shows a warning and job succeeds. It would be nice to have ability to configure job to fail if artifacts are not found.

Proposal

When job artifacts are not found job log shows a warning and job succeeds:

Uploading artifacts...
WARNING: ...: no matching files

It would be nice to have an ability to require artifacts to exist, and fail the job if they don't exit. For example:

  artifacts:
    paths:
    - Debug/*
    require: true

Alternatively:

Add a check that artifacts are within +/- 10% of the size from previous job run (10% is configurable).

Such failure conditions exists in TeamCity: https://confluence.jetbrains.com/display/TCD10/Build+Failure+Conditions#BuildFailureConditions-fail-metric-change

It really saves from a lot of troubles, when some artifact becomes missing due to mis-configuration.

Links / references

Documentation blurb

Overview

Use cases

Who is this for? Provide one or more use cases.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

• Feature assurance
• Documentation
• Added to features.yml

Moving this popular item to the backlog from the untriaged list.

changed milestone to %Backlog

added [deprecated] Accepting merge requests label

added 1 deleted label and removed 1 deleted label

added Category:Continuous Integration label

added grouppipeline execution label

changed milestone to %Backlog

Any chance that you will work on this?

I actually think that the default should have been "require: true" while allowing the user to make them optional. So +1 for getting support for "require : true".

added sectionops label

mentioned in issue gitlab-runner#26868

Any progress in this feature?

Is this issue still active? Hope it will be resolved.

added grouppipeline security label and removed grouppipeline execution label

added Category:Build Artifacts label

Just giving this issue a tiny bump ;)

mentioned in issue #410087

marked this issue as related to gitlab-runner#26868

#22711 might be duplicate of this, or at least with linking as related.

mentioned in issue #22711

Potential workaround

This can be done in .gitlab-ci.yml by adding a job that checks for the artifact file and fails the job with exit 1 if it doesn't exist:

default:
  image: alpine:latest

variables:
  FILE: "some-file.txt" # the file to check for

stages:
  - build
  - check

generate-file:
  stage: build
  script:
    - echo 'some text' >> $FILE # add text to the file
  artifacts:
    paths:
    - $FILE # designate the file as an artifact

job-that-fails-if-file-does-not-exist:
  stage: check
  script:
    - echo "checking for $FILE" # the artifacts from the previous job are available to this one
    - if [ ! -f $FILE ]; then echo "file does not exist, job should fail"
    - exit 1 # exit with non-zero code to fail the job
    - fi
    - echo "file exists, job should pass"

added sectionci label and removed sectionops label

added grouppipeline execution label and removed grouppipeline security label

This is a potential duplicate/solution to #22711.

marked this issue as related to #22711

added Category:Job Artifacts label

Hello. Any update on this topic?

There are several issues that seems to be the same:

• #18921
• #22711
• gitlab-runner#4240

mentioned in issue gitlab-runner#4240

I have a GitLab Ultimate Customer highly interested in this capability.

added customer label