Migrating k8s-testgrid.appspot.com link to testgrid.k8s.io (#7472)

* Migrating k8s-testgrid.appspot.com link to testgrid.k8s.io

Signed-off-by: Ritikaa96 <ritika@india.nec.com>

* Reverting changes from archive folder

Signed-off-by: Ritikaa96 <ritika@india.nec.com>

---------

Signed-off-by: Ritikaa96 <ritika@india.nec.com>
This commit is contained in:
Ritika 2023-11-04 22:11:20 +05:30 committed by GitHub
parent 95b2e0bce7
commit eecb0e740f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions

View File

@ -640,7 +640,7 @@ A quick overview of how we run e2e CI on Kubernetes.
### What is CI?
We run a battery of [release-blocking jobs](https://k8s-testgrid.appspot.com/sig-release-master-blocking)
We run a battery of [release-blocking jobs](https://testgrid.k8s.io/sig-release-master-blocking)
against `HEAD` of the master branch on a continuous basis, and block merges
via [Tide](https://git.k8s.io/test-infra/prow/cmd/tide) on a subset of those
tests if they fail.

View File

@ -68,7 +68,7 @@ SIG Technical Leads
[validation]: /contributors/devel/sig-node/cri-validation.md
[testing policy]: /contributors/devel/sig-node/cri-testing-policy.md
[test grid]: https://k8s-testgrid.appspot.com/sig-node#Summary
[test grid]: https://testgrid.k8s.io/sig-node#Summary
[perf dashboard]: http://node-perf-dash.k8s.io/#/builds
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[readme]: https://github.com/kubernetes/community/tree/master/sig-node

View File

@ -60,7 +60,7 @@ None
SIG Technical Leads
[test grid]: https://k8s-testgrid.appspot.com/sig-scheduling#Summary
[test grid]: https://testgrid.k8s.io/sig-scheduling#Summary
[perf dashboard]: http://perf-dash.k8s.io/
[readme]: https://github.com/kubernetes/community/tree/master/sig-scheduling
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md