-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update Helm release cluster to v0.36.0 #703
Conversation
cluster
v0.36.0.
64d3cd9
to
0c45a40
Compare
cluster
v0.36.0.0c45a40
to
d459384
Compare
cluster
chart to v0.36.0.
There were differences in the rendered Helm template, please check! Output
|
cluster
chart to v0.36.0.
@Gacko Can you please try to avoid excessive force-pushes to apps that trigger E2E tests? There's currently 5 in-progress test runs for this single PR, each one creating 4 test clusters and taking up resources. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I knew it's doing "something" on pushes/updates, but I expected it to trigger tests only when I actually type |
/run cluster-test-suites |
This comment has been minimized.
This comment has been minimized.
Renovate automatically rebases PRs when there are updates available, there is no need to manually do it as Renovate is good at not overloading these most of the time. To ensure that PRs are ready to merge when someone is available we re-trigger the tests on PR resynchronise. |
Sure, but Renovate does not add an entry to the changelog, but sometimes also removes your commits. So I'm kind of lucky the changelog is still there, last time I needed to manually amend a Renovate PR, it didn't work and I first had to fix In the end, I'm sticking with it: I wouldn't expect our tests to trigger for every little event, but only for someone/somewhat really typing |
Also the recent run looks a bit flaky. I can barely imagine the changes from So forgive me, but... /run cluster-test-suites |
I was just trying to make sure you were aware so that we can avoid wasting resource and money where possible. There are limitations with our use of Renovate that we need to account for here. If you have suggestions for improvements of the process then please open an issue for it or discuss it with the team. |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
This PR contains the following updates:
0.35.0
->0.36.0
Trigger E2E tests:
/run cluster-test-suites
Release Notes
giantswarm/cluster (cluster)
v0.36.0
Compare Source
This release removes the
CronJobTimeZone
feature gate as it becomes stable and is included in Kubernetes v1.29.For Kubernetes <v1.29, you will need to re-enable it using the respective values.
Removed
CronJobTimeZone
. (#267)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.