Скачать или смотреть Resolving gitlab build job upload artifacts ERROR: No files to upload Issue in Your Pipeline

Learn how to fix the `No files to upload` error in GitLab CI by properly configuring your artifact paths and project directories.
---
This video is based on the question https://stackoverflow.com/q/77239974/ asked by the user 'Amaranth03' ( https://stackoverflow.com/u/16896271/ ) and on the answer https://stackoverflow.com/a/77241977/ provided by the user 'Raghu' ( https://stackoverflow.com/u/21232051/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: gitlab build job upload artifacts ERROR: No files to upload

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the No files to upload Error in GitLab CI

If you're working with GitLab CI/CD pipelines, you may encounter issues when trying to upload artifacts after a build job. One such error that developers often face is the ERROR: No files to upload message. This commonly arises when the paths specified for the artifacts do not match the actual location of the files you want to store.

In this guide, we'll explore a scenario where a developer faced this issue when attempting to upload .rpm files generated during a build job. We will dissect the error, explain what went wrong, and provide you with a clear solution.

The Issue Explained

The developer posted a configuration for their .gitlab-ci.yml file, aiming to archive build artifacts. Here’s a simplified look at their configuration:

[[See Video to Reveal this Text or Code Snippet]]

However, despite the successful execution of the job and the presence of .rpm files, the GitLab runner logged the following warnings:

[[See Video to Reveal this Text or Code Snippet]]

The crux of the issue was that the specified path to the artifacts was incorrect because the rpmbuild folder was not located under the $CI_PROJECT_DIR directory.

Solution: Understanding Project Directory Structure

To resolve this issue, it’s crucial to understand the difference between the home directory (where the build environment runs) and the $CI_PROJECT_DIR (where GitLab CI/CD expects the project files). Here’s what you need to know:

~ (home directory): This is the default working directory of the GitLab runner.

$CI_PROJECT_DIR: This is the directory where your GitLab project files are stored during the CI job.

Step-by-Step Solution

Create or Move rpmbuild to $CI_PROJECT_DIR: For the artifacts to upload correctly, you need to ensure your rpmbuild directory is within the $CI_PROJECT_DIR. You can either move it or copy it.

Update Your .gitlab-ci.yml Configuration: Here is how to modify the script section in your .gitlab-ci.yml file to include the copying command. This will place rpmbuild in the correct directory:

[[See Video to Reveal this Text or Code Snippet]]

What If You Prefer Moving Instead of Copying?

If you’d rather move the folder instead of copying it, you can use the mv command in your script:

[[See Video to Reveal this Text or Code Snippet]]

Both methods will effectively get your rpmbuild files into the expected location for the artifacts upload.

Conclusion

Encountering the No files to upload error in GitLab CI can be frustrating, but understanding the project directory structure and ensuring your artifact paths are properly aligned can make all the difference. By following the steps outlined in this guide, you should be able to troubleshoot and resolve this issue effectively.

If you have any questions or if there are other issues you'd like to discuss regarding GitLab CI, feel free to leave a comment below!