Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #59165
Closed (moved) (moved)
Open
Issue created Mar 19, 2019 by Julien Lecomte@julien-lecomte

Misleading spurious error when artifacts:reports:junit file does not exist.

Summary

When using gitlab-ci includes, it is often the case that you add more to inherited artifacts to export. When files don't exist, a warning in the job logs will be issued. In the case of a file specified in 'artifacts:reports:junit' does not exist, then a warning then an error is logged and job succeeds.

Steps to reproduce

Create a job with the following:

  artifacts:
    paths:
      - coverage.*
      - public/
    reports:
      junit: public/unitreport.xml
    when: always

You'll get logs like this:

Uploading artifacts...
public/: found 1 matching files
WARNING: coverage.*: no matching files
Uploading artifacts to coordinator... ok id=123456 responseStatus=201 Created token=XXXXXXX
Uploading artifacts...
WARNING: public/unitreport.xml: no matching files
ERROR: No files to upload
Job succeeded

What is the current bug behavior?

WARNING + ERROR and "Job succeeed" is shown. This is confusing.

What is the expected correct behavior?

Only one is shown

Edited Apr 26, 2019 by Julien Lecomte
Assignee
Assign to
Time tracking