publish pipeline to push the Helm Chart to an external repository

[imgios]

Description

Would be good to have a pipeline useful to push each Helm Chart release to an external repository.

Solution you'd like

GitHub pipeline that executes a given set of commands to build the package and push it to an external repository for each commit (e.g. merge a PRs) done on main branch, taking the Chart version from the Chart.yaml:

servarr/Chart.yaml

Line 5 in 42e1a7a

version: 1.0.0

[fonzdm]

Mmh, @imgios, I was thinking about are devops master @lucaam for this... 👀

[lucaam]

Mmh, @imgios, I was thinking about are devops master @lucaam for this... 👀

Challenge accepted ✅

[imgios]

Hi @fonzdm / @lucaam,
I think there is a major question to address before starting with the implementation:

Where do we want to publish the Helm Chart?

I think that we can leverage on ArtifactHub (tldr: the Helm official Repository) to spread the Chart around and make it easily accessible. This can also increase the chance of it getting found from new user. Moreover, we can also leverage to the GitHub Pages to make a "backup" or secondary repository.

In details, my proposal is to have one publish pipeline that is triggered for each commit on the main branch, composed of two jobs:

• publish-artifacthub will be responsible to publish the Helm Chart on ArtifactHub
• publish-pages will be responsible to:
  • Take the Chart from the main branch
  • Move it in a subdirectory named charts
  • Add an index.yml file in the root
  • (optional) Add the robots.txt
  • Deploy the new structure directly on GitHub Pages without using any additional branch

This solution leverages on both GitHub Pages and ArtifactHub, and ease us from managing additional branches.

What do you think?

[fonzdm]

Hi @fonzdm / @lucaam, I think there is a major question to address before starting with the implementation:

Where do we want to publish the Helm Chart?

Since most subcharts we are using as dependencies for Servarr are available and downloaded from ArtifactHub, I would go there as the main repo.

I think that we can leverage on ArtifactHub (tldr: the Helm official Repository) to spread the Chart around and make it easily accessible. This can also increase the chance of it getting found from new user. Moreover, we can also leverage to the GitHub Pages to make a "backup" or secondary repository.

I like this approach, especially because we put all the "packaging and publishing" logic into the pipelines and we do not rely on additional branches to maintain. Anyway, I would focus more on publishing to ArtifactHub and then check if Github Pages are a useful place for us 😄

@lucaam do not panic, @imgios will handle the PR from now on.

[imgios]

Done in #35