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.

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

Fix GHA's release workflow #5694

Merged
merged 1 commit into from
Nov 22, 2022

Conversation

beni0888
Copy link
Collaborator

Signed-off-by: Jesús Benito Calzada [email protected]

Description of the change

This commit fixes the GHA's Release Pipeline. Currently, the workflow is not working properly because the sync_chart_from_bitnami only runs when the pipeline is triggered from the main branch, and it should run when it's triggered from a version tag also.

Benefits

The GHA's Release Pipeline works as expected.

Possible drawbacks

None

Applicable issues

Signed-off-by: Jesús Benito Calzada <[email protected]>
@beni0888 beni0888 self-assigned this Nov 22, 2022
@beni0888 beni0888 added component/ci Issue related to kubeapps ci system github_actions Pull requests that update GitHub Actions code labels Nov 22, 2022
@beni0888 beni0888 added this to the Migrate CI to GitHub Actions milestone Nov 22, 2022
@netlify
Copy link

netlify bot commented Nov 22, 2022

Deploy Preview for kubeapps-dev canceled.

Built without sensitive environment variables

Name Link
🔨 Latest commit cf82e43
🔍 Latest deploy log https://app.netlify.com/sites/kubeapps-dev/deploys/637cf1e0a8b6010008e456cb

@beni0888 beni0888 marked this pull request as ready for review November 22, 2022 16:00
@beni0888 beni0888 merged commit 22e5446 into vmware-tanzu:main Nov 22, 2022
@beni0888 beni0888 deleted the fix-gha-release-workflow branch November 22, 2022 17:15
@@ -617,7 +617,7 @@ jobs:
sync_chart_from_bitnami:
needs:
- setup
if: needs.setup.outputs.running_on_main == 'true'
if: needs.setup.outputs.running_on_main == 'true' || needs.setup.outputs.running_on_tag == 'true'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm still not clear in my mind why we want to sync the bitnami chart each time a PR targets main? Wouldn't we only want to do so if there isn't a PR already open to sync the bitnami chart into our main? (given that the one PR can be recreated or just have latest changes merged etc?)

Thanks either way!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-not-required component/ci Issue related to kubeapps ci system github_actions Pull requests that update GitHub Actions code
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants