Hi @wojtek,

Can you describe the use case and how you would use the implemented feature? Please include as much detail as possible in order to understand your use case.

Well, helm chart is just a package, it has certain requirements: https://v2.helm.sh/docs/chart_repository/

Currently even 1dev points it's chart (https://artifacthub.io/packages/helm/onedev/onedev) to https://dl.cloudsmith.io/public/onedev/onedev/helm/charts/ (which gives 404 btw…)

In a nutshell, as the documentation indicates - it's just a simple index file and list of (helm chart) archives.

Adding to the issue - hosting helm-charts would be akin hosting other types of packages like docker images, maven artifacts and similar (could/should fit into "Packages" section (https://code.onedev.io/onedev/server/~packages).

As with other types of packages: on the one hand it's convenient to self-host artifacts/packages (gives control) but on the other, and this is more crucial - global helm chart repository (artifacthub.io) doesn't store any packages, it's serves more like a "library" of packages pointing to the exact location, and in this instance 1dev would be that location.

EDIT: As to why having artifact/helm chat repository - it makes installation under k8s easier - both in terms of upgrading and rolling back to previous version (if there is only binary difference without database schema changes) - most of the time it's a matter of simple clicking "upgrade" or "rollback". Without dedicated helm chart repository that can be published to artifactory it's makes it slightly more difficutl.

State changed as code fixing the issue is committed (02d85f24)

State changed as build OD-6133 is successful