CI/CD Container scanning - problem with SBOM upload

DevSecOps
1

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

ogin Succeeded 73$ docker login "$GITLAB_CI_REGISTRY_URL" -u "$GITLAB_CI_USERNAME" -p "$GITLAB_CI_PASSWORD" 74WARNING! Using --password via the CLI is insecure. Use --password-stdin. 75WARNING! Your password will be stored unencrypted in /root/.docker/config.json. 76Configure a credential helper to remove this warning. See 77https://docs.docker.com/engine/reference/commandline/login/#credentials-store 78Login Succeeded 79$ gtcs scan 80bash: gtcs: command not found 81Uploading artifacts for failed job00:01 82Uploading artifacts... 83Runtime platform arch=amd64 os=linux pid=307657 revision=44feccdf version=17.0.0 84WARNING: */gl-sbom-.cdx.json: no matching files. Ensure that the artifact path is relative to the working directory (/root/builds/GnMpf7nx_/0/root/linux) 85ERROR: No files to upload 86Uploading artifacts... 87Runtime platform arch=amd64 os=linux pid=307667 revision=44feccdf version=17.0.0 88WARNING: gl-container-scanning-report.json: no matching files. Ensure that the artifact path is relative to the working directory (/root/builds/GnMpf7nx_/0/root/linux) 89ERROR: No files to upload 90Uploading artifacts... 91Runtime platform arch=amd64 os=linux pid=307690 revision=44feccdf version=17.0.0 92WARNING: gl-dependency-scanning-report.json: no matching files. Ensure that the artifact path is relative to the working directory (/root/builds/GnMpf7nx_/0/root/linux) 93ERROR: No files to upload 94ERROR: Job failed: exit status 1

Describe your question in as much detail as possible:

  • What are you seeing, and how does that differ from what you expect to see?
  • Consider including screenshots, error messages, and/or other helpful visuals

Steps to reproduce

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

Configuration

Provide screenshots from the GitLab UI showing relevant configuration, if applicable.
On self-managed instances, add the relevant configuration settings or changes.

Versions

Please select whether options apply, and add the version information.

Versions

Helpful resources

  1. Before opening a new topic, make sure to search for keywords in the forum search
  2. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  3. Troubleshooting docs: Self-managed GitLab instances.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

2

@yashmahajan01 I’ve edited your topic title to what I believe the error message says. Please edit your post, and and fill in the remaining questions from the template. These details will help with providing ideas and suggestions more efficiently. Thanks.