# Renaming from jetstack/testing to cert-manager/testing
We first renamed the repo.
Then, in the `testing` repository, we have renamed everything from github.com/jetstack/testing to github.com/cert-manager/testing.
Then, we have looked at the diff between the live configuration and our local changes:
```console
$ cd ../config/ && \
kubectl create configmap config --from-file=config.yaml=config.yaml --dry-run=client -o yaml | kubectl diff -f -
diff -u -N /tmp/LIVE-2065410493/v1.ConfigMap.default.config /tmp/MERGED-3021271460/v1.ConfigMap.default.config
--- /tmp/LIVE-2065410493/v1.ConfigMap.default.config 2023-08-31 15:09:04.966446453 +0200
+++ /tmp/MERGED-3021271460/v1.ConfigMap.default.config 2023-08-31 15:09:04.966446453 +0200
@@ -242,7 +242,7 @@
- do-not-merge/release-note-label-needed
# Maintain separate testing configuration as PRs in this repo don't need release note
- repos:
- - jetstack/testing
+ - cert-manager/testing
labels:
- lgtm
- approved
make: *** [Makefile:29: diff-config] Error 1
```
and
```console
$ cd ../config/ && \
kubectl create configmap plugins --from-file=plugins.yaml=plugins.yaml --dry-run=client -o yaml | kubectl diff -f -
diff -u -N /tmp/LIVE-3119272648/v1.ConfigMap.default.plugins /tmp/MERGED-1888461632/v1.ConfigMap.default.plugins
--- /tmp/LIVE-3119272648/v1.ConfigMap.default.plugins 2023-08-31 15:09:14.722403828 +0200
+++ /tmp/MERGED-1888461632/v1.ConfigMap.default.plugins 2023-08-31 15:09:14.722403828 +0200
@@ -1,6 +1,5 @@
apiVersion: v1
data:
- VERSION: 61b7fa9c624052f05fc9b0f0bc07a92c7b0ae084
plugins.yaml: |
# Plugin repository whitelist.
# Keys: Full repo name: "org/repo".
@@ -8,9 +7,7 @@
---
triggers:
- repos:
- - jetstack/testing
- only_org_members: true
- - repos:
+ - cert-manager/testing
- cert-manager/cert-manager
- cert-manager/website
- cert-manager/trust-manager
@@ -157,7 +154,7 @@
plugins:
- release-note
- jetstack/testing:
+ cert-manager/testing:
plugins:
- approve
- config-updater
make: *** [Makefile:41: diff-plugins] Error 1
```
Since the changes looked OK, we applied them using:
```bash
```
Then, we wanted to know if the configuration change was effective by reloading one of the services:
```bash
kubectl rollout restart deployment statusreconciler
```
```console
$ kubectl logs -l app=statusreconciler
{"component":"status-reconciler","config_revision":"","file":"k8s.io/test-infra/prow/statusreconciler/controller.go:431","func":"k8s.io/test-infra/prow/statusreconciler.removedPresubmits","level":"info","msg":"Identified 0 removed blocking presubmits.","old_config_revision":"98639fe4889e77c04238cb9eb84883be0d4c95d6","severity":"info","time":"2023-08-31T13:10:16Z"}
{"component":"status-reconciler","config_revision":"","file":"k8s.io/test-infra/prow/statusreconciler/controller.go:471","func":"k8s.io/test-infra/prow/statusreconciler.migratedBlockingPresubmits","level":"info","msg":"Identified 0 migrated blocking presubmits.","old_config_revision":"98639fe4889e77c04238cb9eb84883be0d4c95d6","severity":"info","time":"2023-08-31T13:10:16Z"}
{"component":"status-reconciler","config_revision":"","duration":"667.875µs","file":"k8s.io/test-infra/prow/statusreconciler/controller.go:176","func":"k8s.io/test-infra/prow/statusreconciler.(*Controller).Run","level":"info","msg":"Statuses reconciled","old_config_revision":"98639fe4889e77c04238cb9eb84883be0d4c95d6","severity":"info","time":"2023-08-31T13:10:16Z"}
{"component":"status-reconciler","error":"plugins [approve dco owners-label verify-owners] are duplicated for cert-manager/testing and cert-manager","file":"k8s.io/test-infra/prow/plugins/plugins.go:393","func":"k8s.io/test-infra/prow/plugins.(*ConfigAgent).Start.func1","level":"error","msg":"Error loading plugin config.","path":"/etc/plugins/plugins.yaml","severity":"error","time":"2023-08-31T13:10:43Z"}
{"component":"status-reconciler","error":"plugins [approve dco owners-label verify-owners] are duplicated for cert-manager/testing and cert-manager","file":"k8s.io/test-infra/prow/plugins/plugins.go:393","func":"k8s.io/test-infra/prow/plugins.(*ConfigAgent).Start.func1","level":"error","msg":"Error loading plugin config.","path":"/etc/plugins/plugins.yaml","severity":"error","time":"2023-08-31T13:11:43Z"}
```
We have then removed some configuration in `config.yml` that we thought was useless:
Now, the statusreconciler isn't complaining anymore:
```console
$ kubectl logs -l app=statusreconciler
{"component":"status-reconciler","config_revision":"","duration":"126.779µs","file":"k8s.io/test-infra/prow/statusreconciler/controller.go:176","func":"k8s.io/test-infra/prow/statusreconciler.(*Controller).Run","level":"info","msg":"Statuses reconciled","old_config_revision":"","severity":"info","time":"2023-08-31T13:14:15Z"}
```
We have then tested the branchprotector job by running it manually like so:
Since it worked, we were OK with branchprotector.
Then, we needed Tide to work again to be able to merge PRs.
```bash
kubectl rollout restart deployment tide
```
```console
$ kubectl logs -l app=tide
{"component":"tide","controller":"status-update","file":"k8s.io/test-infra/prow/tide/status.go:662","func":"k8s.io/test-infra/prow/tide.(*statusController).search.func1","level":"info","msg":"Query changed, resetting start time to zero","previously":"","query":" is:pr state:open sort:updated-asc archived:false org:\"cert-manager\" repo:\"cert-manager/cert-manager\" repo:\"cert-manager/testing\"","severity":"info","time":"2023-08-31T13:19:54Z"}
```
We have then approved and lgtm the PR.
We realized that we had forgotten to change the ProwJobs, so we triggered the `config-updater` plugin by lgtm'ing a PR (https://github.com/cert-manager/testing/pull/903).
Sign in with Wallet
Connect another wallet