Update jobs to 1.9

[maelvls]

Based on:

• Bump prow configuration after cert-manager 1.7 release #620

I also did the following:

• I moved all the cert-mananger-release-next-periodics and cert-mananger-periodics to make since I think we don't need to keep Bazel running on those;
• I did not change anything (appart from changing the branch release-1.8 to release-1.9) in cert-manager-presubmits since that may break when releasing older versions of cert-manager.

[SgtCoDFish]

(on my phone on a train, sorry for bad formatting and short comments!)

[SgtCoDFish]

Suggestion: as I mentioned in the 1.8.0 release thread on slack, I didn't create release-1.9. We can just test master here

[maelvls]

I agree, let’s get rid of release-1.9 for now until we do an alpha release. I explained and fixed this in eb52868.

[SgtCoDFish]

We're also missing updates to the old presubmits and periodics, e.g.: https://github.com/jetstack/testing/blob/master/config/jobs/cert-manager/cert-manager/release-previous/cert-manager-release-previous-periodics.yaml

We need to test both release-1.7 and release-1.8 for release-previous

[SgtCoDFish]

/lgtm
/approve

I think any other changes we need can easily come in a separate PR, this looks good! Thanks

[SgtCoDFish]

nit(non-blocking): grammar

Suggested change

	# We don't need periodically testing the release-next breanch (e.g., the
	# "release-1.9" branch) until we release the first alpha (e.g.,
	# "1.9.0-alpha.0"). Since we can't "deactivate" the release-next periodics
	# jobs until we have an alpha (there is no "skip" field on the ProwJob
	# object), we just remove all of the jobs from this file. That's why the
	# below array is empty. See Step 13.3 in
	# https://cert-manager.io/docs/contributing/release-process/
	# We don't need to periodically test the release-next breanch (e.g., the
	# "release-1.9" branch) until we release the first alpha (e.g.,
	# "1.9.0-alpha.0"). Since we can't "deactivate" the release-next periodics
	# jobs until we have an alpha (there is no "skip" field on the ProwJob
	# object), we just remove all of the jobs from this file. That's why the
	# below array is empty. See Step 13.3 in
	# https://cert-manager.io/docs/contributing/release-process/

[maelvls]

Oops, good catch. Thanks. I'll fix that the next time I get to edit this file if that's OK

[SgtCoDFish]

It's all good, I'm fixing it in the PR I'm working on for release-previous 👍

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maelvls, SgtCoDFish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/jobs/cert-manager/OWNERS [SgtCoDFish,maelvls]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jetstack-bot]

@maelvls: Updated the job-config configmap in namespace default at cluster default using the following files:

• key cert-manager-periodics.yaml using file config/jobs/cert-manager/cert-manager/cert-manager-periodics.yaml
• key cert-manager-presubmits.yaml using file config/jobs/cert-manager/cert-manager/cert-manager-presubmits.yaml
• key cert-manager-release-next-periodics.yaml using file config/jobs/cert-manager/cert-manager/release-next/cert-manager-release-next-periodics.yaml

Details

In response to this:

Based on:

• Bump prow configuration after cert-manager 1.7 release #620

I also did the following:

• I moved all the cert-mananger-release-next-periodics and cert-mananger-periodics to make since I think we don't need to keep Bazel running on those;
• I did not change anything (appart from changing the branch release-1.8 to release-1.9) in cert-manager-presubmits since that may break when releasing older versions of cert-manager.

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/test-infra repository.