Ability to require artifacts to exists and fail the job otherwise

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

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.

Edited by 🤖 GitLab Bot 🤖