Swap periodic-kubernetes-bazel-test-master for canary

[ameukam]

Migrate:

https://testgrid.k8s.io/sig-release-master-blocking#bazel-build-master
https://testgrid.k8s.io/sig-release-master-blocking#bazel-test-master

Signed-off-by: Arnaud Meukam ameukam@gmail.com

ref: kubernetes/k8s.io#841

/assign @spiffxp @BenTheElder
/wg k8s-infra

[k8s-ci-robot]

@ameukam: The label(s) wg/ cannot be applied, because the repository doesn't have them

In response to this:

Migrate:

https://testgrid.k8s.io/sig-release-master-blocking#bazel-build-master
https://testgrid.k8s.io/sig-release-master-blocking#bazel-test-master

Signed-off-by: Arnaud Meukam ameukam@gmail.com

ref: kubernetes/k8s.io#841

/assign @spiffxp @BenTheElder
/wg k8s-infra

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.

[spiffxp]

/hold
These can't be migrated as-is. See the description of kubernetes/k8s.io#846 for why build can't be migrated, and it's going to require more effort than releng has bandwidth for in 1.19

I'm confirming test can run without RBE via #18607; if that works, then you would do the same for test

[BenTheElder]

/hold
double-hold :-)

super appreciate the effort, the issue is that a major side-effect of these jobs is keeping the bazel cache warm, for use in presubmits
that cache is not cross cluster, and most of the presubmit jobs using the cache can't be moved yet.

we should probably coordinate merging this with being ready to move the rest of the bazel using presubmits

[spiffxp]

a major side-effect of these jobs is keeping the bazel cache warm, for use in presubmits

Hmm, TIL. Are there any other jobs that could serve a similar role? Like pull-kubernetes-e2e-gce or something? Or would we want to consider triggering a non-reporting equivalent of this job on k8s-infra-prow-build?

[spiffxp]

(I guess I'm effectively keeping k8s-infra-prow-build's bazel cache warm by having migrated periodic-kubernetes-bazel-test-canary over there)

[BenTheElder]

it's important that it be a frequent post-submit. the cache is not aware of presubmit vs potsubmit usage, so we want postsubmit / periodic to be reasonably frequent, so as the cache is not drowned out by random PR changes. eviction is based on least recently accessed.

…

On Mon, Aug 3, 2020 at 6:07 PM Aaron Crickenberger ***@***.***> wrote: (I guess I'm effectively keeping k8s-infra-prow-build's bazel cache warm by having migrated periodic-kubernetes-bazel-test-canary over there) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18613 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHADK65SSKCNTN2AJCHIETR65NMHANCNFSM4PSXZ4GA> .

[BenTheElder]

we might be able to disable writes from presubmit, but that is not currently in effect today. On Mon, Aug 3, 2020 at 7:19 PM Benjamin Elder <bentheelder@google.com> wrote:

…

it's important that it be a frequent post-submit. the cache is not aware of presubmit vs potsubmit usage, so we want postsubmit / periodic to be reasonably frequent, so as the cache is not drowned out by random PR changes. eviction is based on least recently accessed. On Mon, Aug 3, 2020 at 6:07 PM Aaron Crickenberger < ***@***.***> wrote: > (I guess I'm effectively keeping k8s-infra-prow-build's bazel cache warm > by having migrated periodic-kubernetes-bazel-test-canary over there) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#18613 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAHADK65SSKCNTN2AJCHIETR65NMHANCNFSM4PSXZ4GA> > . >

[spiffxp]

Well, at this point then, I'd like to suggest @ameukam change this PR to do the following:

• rebase to pick up the changes introduced in Alter bazel-test-canary to run on k8s-infa-prow-build #18607
• leave periodic-kubernetes-bazel-build-master untouched
• swap the names of the bazel-test jobs such that
  • periodic-kubernetes-bazel-test-canary = the job that runs on k8s-prow-builds, uses RBE, and is on sig-testing-canaries dashboard
  • periodic-kubernetes-bazel-test-master = the job that runs on k8s-infra-prow-build and is release-blocking

This will leave k8s-prow-builds' bazel cache getting the exact same amount of coverage, while moving the release-blocking test job to a dedicated cluster

[spiffxp]

@ameukam if you redo this as I described, that should take care of #18652

[ameukam]

@spiffxp I updated the PR based on my understanding of what you came up with.

[spiffxp]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam, spiffxp

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/OWNERS [spiffxp]

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

[spiffxp]

/retitle Swap periodic-kubernetes-bazel-test-master for canary

[spiffxp]

/hold cancel

[k8s-ci-robot]

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

• key bazel-build-test.yaml using file config/jobs/kubernetes/sig-testing/bazel-build-test.yaml

In response to this:

Migrate:

https://testgrid.k8s.io/sig-release-master-blocking#bazel-build-master
https://testgrid.k8s.io/sig-release-master-blocking#bazel-test-master

Signed-off-by: Arnaud Meukam ameukam@gmail.com

ref: kubernetes/k8s.io#841

/assign @spiffxp @BenTheElder
/wg k8s-infra

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.