Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Include note in release process about chart publishing per image. #5962

Merged
merged 1 commit into from
Feb 8, 2023
Merged

Include note in release process about chart publishing per image. #5962

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions site/content/docs/latest/reference/developer/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -206,6 +206,10 @@ Even though we have a thorough test suite in our repository, we still _must_ per

Next, create a tag for the aforementioned commit and push it to the remote repository. Please note that the tag name will be used as the release name.

> When a new tag is detected, Bitnami will automatically build a set of container images based on the tagged commit. They later will be published in [the Bitnami Dockerhub image registry](https://hub.docker.com/search?q=bitnami%2Fkubeapps&type=image).
> Please note that this workflow is run outside the control of the Kubeapps release process.
> Please note also that the Bitnami Catalog will publish a version of the chart whenever one (single) image is published, which means that we need to be careful if any Kubeapps component updates are interdependent, perhaps requesting the Kubeapps chart publishing be paused until all images are published.

For doing so, run the following commands:

```bash
Expand All @@ -226,9 +230,6 @@ An example of the triggered workflow is depicted below:

![CI workflow after pushing a new tag](../../img/ci-workflow-release.png "CI workflow after pushing a new tag")

> When a new tag is detected, Bitnami will automatically build a set of container images based on the tagged commit. They later will be published in [the Bitnami Dockerhub image registry](https://hub.docker.com/search?q=bitnami%2Fkubeapps&type=image).
> Please note that this workflow is run outside the control of the Kubeapps release process

## 3 - Complete the GitHub release notes

Once the release job is finished, you will have a pre-populated [draft GitHub release](https://github.com/vmware-tanzu/kubeapps/releases).
Expand Down