Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Abandoned
    • None
    • None
    • release
    • None

    Description

      Up to latest version

      Attachments

        Activity

          wwei Weiwei Yang added a comment -

          And I think we should look at how to automate this

          wwei Weiwei Yang added a comment - And I think we should look at how to automate this
          kmarton Kinga Marton added a comment - - edited

          wwei I don't think it is a good idea to publish the latest charts on Helm hub. It is changing frequently and even if it is just one command and one commit, it is annoying that we have to perform it manually each time something is changed. The idea for having the latest charts was to make our work during development/testing easier, but if it means that we should change the package each time something is changed I don't think it worth it. 

          Also we will have troubles with the versioning as well, since helm will accept only 3 difit version, so right now we are using 0.9.0 version for the latest version, what is wrong and may cause a lot of misunderstandings.

          My suggestion is to publish only the charts for the released versions and remove the latest one. During development we can use the charts from the release repository.

          wwei, wilfreds, adam.antal, rreti what do you think?

          kmarton Kinga Marton added a comment - - edited wwei  I don't think it is a good idea to publish the latest charts on Helm hub. It is changing frequently and even if it is just one command and one commit, it is annoying that we have to perform it manually each time something is changed. The idea for having the latest charts was to make our work during development/testing easier, but if it means that we should change the package each time something is changed I don't think it worth it.  Also we will have troubles with the versioning as well, since helm will accept only 3 difit version, so right now we are using 0.9.0 version for the latest version, what is wrong and may cause a lot of misunderstandings. My suggestion is to publish only the charts for the released versions and remove the latest one. During development we can use the charts from the release repository. wwei , wilfreds , adam.antal , rreti  what do you think?
          wwei Weiwei Yang added a comment -

          It makes sense to only publish the released versions of helm charts to the helm hub.
          But we still need to publish the latest version of helm charts somewhere because our e2e test is consuming it. Maybe we can publish onto our release repo, as a tarball. We can think about how to automate this with a proper github workflow action.

          wwei Weiwei Yang added a comment - It makes sense to only publish the released versions of helm charts to the helm hub. But we still need to publish the latest version of helm charts somewhere because our e2e test is consuming it. Maybe we can publish onto our release repo, as a tarball. We can think about how to automate this with a proper github workflow action.
          wwei Weiwei Yang added a comment -

          Since we have modified our e2e test script to download helm chart directly from the release repo, this is no longer needed. Closing now.

          wwei Weiwei Yang added a comment - Since we have modified our e2e test script to download helm chart directly from the release repo, this is no longer needed. Closing now.

          People

            kmarton Kinga Marton
            wwei Weiwei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: