From 949d5573365443ab2df839d7528543d2f44a25e0 Mon Sep 17 00:00:00 2001 From: Abhijeet Gaurav <65087356+abhijeetgauravm@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:43:14 +0530 Subject: [PATCH 1/3] fixed broken links of testgrid dashboard in README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c5e5a05f72e..586c1f3718f 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ Please refer to [development guide](./docs/csi-dev.md) ### View CI Results - testgrid [sig-storage-csi-smb](https://testgrid.k8s.io/sig-storage-csi-other) dashboard. - - Driver image build pipeline: [post-csi-driver-smb-push-images](https://k8s-testgrid.appspot.com/sig-storage-image-build#post-csi-driver-smb-push-images) + - Driver image build pipeline: [post-csi-driver-smb-push-images](https://testgrid.k8s.io/sig-storage-image-build#post-csi-driver-smb-push-images) ### Links - [SMB FlexVolume driver](https://github.com/Azure/kubernetes-volume-drivers/tree/master/flexvolume/smb) From 0ff82aaaad55f3f3f29b502d3f189fadd07190d1 Mon Sep 17 00:00:00 2001 From: Abhijeet Gaurav <65087356+abhijeetgauravm@users.noreply.github.com> Date: Mon, 21 Aug 2023 17:47:50 +0530 Subject: [PATCH 2/3] fixed broken links of testgrid dashboard in SIDECAR_RELEASE_PROCESS.md --- release-tools/SIDECAR_RELEASE_PROCESS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/release-tools/SIDECAR_RELEASE_PROCESS.md b/release-tools/SIDECAR_RELEASE_PROCESS.md index 0e3d516a5ea..41e8b6a6d7c 100644 --- a/release-tools/SIDECAR_RELEASE_PROCESS.md +++ b/release-tools/SIDECAR_RELEASE_PROCESS.md @@ -17,7 +17,7 @@ The release manager must: Whenever a new Kubernetes minor version is released, our kubernetes-csi CI jobs must be updated. -[Our CI jobs](https://k8s-testgrid.appspot.com/sig-storage-csi-ci) have the +[Our CI jobs](https://testgrid.k8s.io/sig-storage-csi-ci) have the naming convention `-on-`. 1. Jobs should be actively monitored to find and fix failures in sidecars and @@ -90,10 +90,10 @@ naming convention `-on-`. 1. Submit a PR for README changes, in particular, Compatibility, Feature status, and any other sections that may need updating. 1. Check that all [canary CI - jobs](https://k8s-testgrid.appspot.com/sig-storage-csi-ci) are passing, + jobs](https://testgrid.k8s.io/sig-storage-csi-ci) are passing, and that test coverage is adequate for the changes that are going into the release. 1. Check that the post-\-push-images builds are succeeding. - [Example](https://k8s-testgrid.appspot.com/sig-storage-image-build#post-external-snapshotter-push-images) + [Example](https://testgrid.k8s.io/sig-storage-image-build#post-external-snapshotter-push-images) 1. Make sure that no new PRs have merged in the meantime, and no PRs are in flight and soon to be merged. 1. Create a new release following a previous release as a template. Be sure to select the correct @@ -101,7 +101,7 @@ naming convention `-on-`. [external-provisioner example](https://github.com/kubernetes-csi/external-provisioner/releases/new) 1. If release was a new major/minor version, create a new `release-` branch at that commit. -1. Check [image build status](https://k8s-testgrid.appspot.com/sig-storage-image-build). +1. Check [image build status](https://testgrid.k8s.io/sig-storage-image-build). 1. Promote images from k8s-staging-sig-storage to registry.k8s.io/sig-storage. From the [k8s image repo](https://github.com/kubernetes/k8s.io/tree/HEAD/registry.k8s.io/images/k8s-staging-sig-storage), @@ -120,7 +120,7 @@ naming convention `-on-`. The following jobs are triggered after tagging to produce the corresponding image(s): -https://k8s-testgrid.appspot.com/sig-storage-image-build +https://testgrid.k8s.io/sig-storage-image-build Clicking on a failed build job opens that job in https://prow.k8s.io. Next to the job title is a rerun icon (circle with arrow). Clicking it opens a popup From 248ea99ef28620fbb331a8b1afdc670dfc2a9b7a Mon Sep 17 00:00:00 2001 From: Abhijeet Gaurav <65087356+abhijeetgauravm@users.noreply.github.com> Date: Mon, 21 Aug 2023 20:00:58 +0530 Subject: [PATCH 3/3] Updated the changes in release tools SIDECAR_RELEASE_PROCESS.md --- release-tools/SIDECAR_RELEASE_PROCESS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/release-tools/SIDECAR_RELEASE_PROCESS.md b/release-tools/SIDECAR_RELEASE_PROCESS.md index 41e8b6a6d7c..0e3d516a5ea 100644 --- a/release-tools/SIDECAR_RELEASE_PROCESS.md +++ b/release-tools/SIDECAR_RELEASE_PROCESS.md @@ -17,7 +17,7 @@ The release manager must: Whenever a new Kubernetes minor version is released, our kubernetes-csi CI jobs must be updated. -[Our CI jobs](https://testgrid.k8s.io/sig-storage-csi-ci) have the +[Our CI jobs](https://k8s-testgrid.appspot.com/sig-storage-csi-ci) have the naming convention `-on-`. 1. Jobs should be actively monitored to find and fix failures in sidecars and @@ -90,10 +90,10 @@ naming convention `-on-`. 1. Submit a PR for README changes, in particular, Compatibility, Feature status, and any other sections that may need updating. 1. Check that all [canary CI - jobs](https://testgrid.k8s.io/sig-storage-csi-ci) are passing, + jobs](https://k8s-testgrid.appspot.com/sig-storage-csi-ci) are passing, and that test coverage is adequate for the changes that are going into the release. 1. Check that the post-\-push-images builds are succeeding. - [Example](https://testgrid.k8s.io/sig-storage-image-build#post-external-snapshotter-push-images) + [Example](https://k8s-testgrid.appspot.com/sig-storage-image-build#post-external-snapshotter-push-images) 1. Make sure that no new PRs have merged in the meantime, and no PRs are in flight and soon to be merged. 1. Create a new release following a previous release as a template. Be sure to select the correct @@ -101,7 +101,7 @@ naming convention `-on-`. [external-provisioner example](https://github.com/kubernetes-csi/external-provisioner/releases/new) 1. If release was a new major/minor version, create a new `release-` branch at that commit. -1. Check [image build status](https://testgrid.k8s.io/sig-storage-image-build). +1. Check [image build status](https://k8s-testgrid.appspot.com/sig-storage-image-build). 1. Promote images from k8s-staging-sig-storage to registry.k8s.io/sig-storage. From the [k8s image repo](https://github.com/kubernetes/k8s.io/tree/HEAD/registry.k8s.io/images/k8s-staging-sig-storage), @@ -120,7 +120,7 @@ naming convention `-on-`. The following jobs are triggered after tagging to produce the corresponding image(s): -https://testgrid.k8s.io/sig-storage-image-build +https://k8s-testgrid.appspot.com/sig-storage-image-build Clicking on a failed build job opens that job in https://prow.k8s.io. Next to the job title is a rerun icon (circle with arrow). Clicking it opens a popup