-
Notifications
You must be signed in to change notification settings - Fork 237
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
Migrate to Community CI By August 1st #1747
Comments
kubernetes/test-infra#32887 Merged! |
@ArangoGutierrez: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
You should probably double check that the e2e job is still working, in particular, it might need some follow-ups. |
you are right, celebrating too fast.... |
@ArangoGutierrez: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
since it's a postsubmit, we won't know until a PR merges. I could manually trigger it to run again for an existing merge but with the latest config, let's try that ... |
If we check the events for the failed run:
Whatever this secret was enabling will need to be replicated using only what is provided by the k8s community infra. I don't have context on what this job attempts to do and why it had a custom secret. Does anyone know what this secret was for? If it's just to use a GCP project, you can instead rent one from boskos, kubetest(2) provide facilities for this. it actually kinda looks like https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/scripts/test-infra/test-e2e.sh is doing things on AWS? |
in which case we should move it to the EKS cluster and figure out how to replicate the infra over there (not my speciality but .. we can reach out in #sig-k8s-infra) |
#1763 is the last bit |
Merged! |
Thanks! |
Node feature discovery CI still needs migrating, per https://groups.google.com/a/kubernetes.io/g/dev/c/p6PAML90ZOU
You can find jobs listed in:
https://github.com/kubernetes/test-infra/blob/master/docs/job-migration-todo.md
(see e.g. jobs with name containing "node-feature-discovery")
The text was updated successfully, but these errors were encountered: