Disable redundant pull-containerd-build job

[chrishenzie]

This job's function of building containerd artifacts on pull requests is already covered by the binaries job in containerd's GitHub Actions: https://github.com/containerd/containerd/blob/v2.1.3/.github/workflows/ci.yml#L183

Disabling this job is a step towards the larger goal of migrating containerd's CI off of the community-owned prow.k8s.io infrastructure.

Disabling this job by setting always_run: false and optional: true as a non-disruptive first step before its eventual removal.

/assign @BenTheElder

[BenTheElder]

/approve
/hold

[kannon92]

/lgtm

@BenTheElder any reason for the hold?

Can we merge this?

[BenTheElder]

@BenTheElder any reason for the hold?

Just to let someone else from containerd take a look [note also no lgtm].

Usually if a hold is meant to have particular requirements we spell them out, that was just "I don't have full context but this test-infra change looks OK"

/hold-cancel

[dmcgowan]

Makes sense, shouldn't be anything on containerd side relying on it

[k8s-ci-robot]

@dmcgowan: changing LGTM is restricted to collaborators

In response to this:

Makes sense, shouldn't be anything on containerd side relying on it

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, chrishenzie, dmcgowan

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/jobs/containerd/containerd/OWNERS [BenTheElder]

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

[BenTheElder]

/hold cancel

[k8s-ci-robot]

@chrishenzie: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key containerd-presubmit-jobs.yaml using file config/jobs/containerd/containerd/containerd-presubmit-jobs.yaml

In response to this:

This job's function of building containerd artifacts on pull requests is already covered by the binaries job in containerd's GitHub Actions: https://github.com/containerd/containerd/blob/v2.1.3/.github/workflows/ci.yml#L183

Disabling this job is a step towards the larger goal of migrating containerd's CI off of the community-owned prow.k8s.io infrastructure.

Disabling this job by setting always_run: false and optional: true as a non-disruptive first step before its eventual removal.

/assign @BenTheElder

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-sigs/prow repository.

[mikebrow]

This job's function of building containerd artifacts on pull requests is already covered by the binaries job in containerd's GitHub Actions: https://github.com/containerd/containerd/blob/v2.1.3/.github/workflows/ci.yml#L183

Disabling this job is a step towards the larger goal of migrating containerd's CI off of the community-owned prow.k8s.io infrastructure.

Disabling this job by setting always_run: false and optional: true as a non-disruptive first step before its eventual removal.

/assign @BenTheElder

nod we put it in there as insurance for prow .. why run the bigger job if build fails.. also at one point I believe the build output was cached.. May have been lost in the process of moving off prior ci tooling