Skip to content

Using CI Component on self hosted and getting "the component path is not supported."

Summary

I struggle to use my own CI component on my self hosted giltab instance. The pipeline editor and the pipeline itself give this error: This GitLab CI configuration is invalid: component 'https://OUR_SERVER_IP/jlammering/container-scanning-component/container_scanning@0.2' - the component path is not supported. Learn more . OUR_IP_OF_THE_SERVER is a placeholder just for this forum to not publish our IP. But it has to be noticed that we use an IP int his form (XXX.XX.XXX.XXX) and not a DNS name for our instance.

Steps to reproduce

  • have a self hosted instance
  • publish a component
  • try to use it

Example Project

Using gitlab 16.7. I published the component in a component project with this path: https://OUR_SERVER_IP/jlammering/container-scanning-component and this template file: grafik The overall structure is this: grafik

This is the release: grafik

Here you can see it in the Component Catalog: grafik

This is how i try to use it:

include:
  - component: https://OUR_SERVER_IP/jlammering/container-scanning-component/container_scanning@0.2

What is the current bug behavior?

Pipeline says This GitLab CI configuration is invalid: component 'https://OUR_SERVER_IP/jlammering/container-scanning-component/container_scanning@0.2' - the component path is not supported.

What is the expected correct behavior?

It should just find the component and use it.