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

[Backport v2.8] Reduce reliance on Rancher Git mirror for running CI tests #45677

Closed
snasovich opened this issue Jun 4, 2024 · 4 comments
Closed
Assignees
Labels
area/test area/testing kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. QA/None Indicates that the task or issue does not need QA. team/fleet team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support
Milestone

Comments

@snasovich
Copy link
Collaborator

Backport of #45676 to release/v2.8 branch.

Note this will require backporting #43530 to release/v2.8 first if the approach suggested on the referenced issue is chosen.

@snasovich snasovich added area/test team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. team/fleet QA/None Indicates that the task or issue does not need QA. area/testing labels Jun 4, 2024
@snasovich snasovich added this to the v2.8-Next1 milestone Jun 4, 2024
@snasovich
Copy link
Collaborator Author

Currently blocked on getting #43530 backported to release/v2.8.
@olblak @kkaempf , is this something your team can take care of or there are concerns with migrating that improvement to v2.8 line of releases?

@weyfonk
Copy link
Contributor

weyfonk commented Jun 6, 2024

Currently blocked on getting #43530 backported to release/v2.8. @olblak @kkaempf , is this something your team can take care of or there are concerns with migrating that improvement to v2.8 line of releases?

See #45699.

@snasovich
Copy link
Collaborator Author

Moved to "Actively QAing" while builds are running. Will close as soon there is confirmation CI stability is not negatively affected by this change.

@snasovich
Copy link
Collaborator Author

Closing as there are no known reports of this change causing CI issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test area/testing kind/tech-debt Formerly issues labeled as ci-improvements, tasks, flaky tests, and post-release. QA/None Indicates that the task or issue does not need QA. team/fleet team/hostbusters The team that is responsible for provisioning/managing downstream clusters + K8s version support
Projects
None yet
Development

No branches or pull requests

2 participants