containerd binaries are not bundled in release tarballs

[jamieklassen]

Problem

unzipping https://github.com/concourse/concourse/releases/download/v6.4.1/concourse-6.4.1-linux-amd64.tgz you don't see any containerd binaries, but unzipping https://storage.googleapis.com/concourse-artifacts/dev/concourse-6.4.0%2Bdev.277.4dd4ee3.linux.amd64.tgz you do.

Proposed solution

add some get steps for the containerd binaries around here:

ci/pipelines/release-v6.yml

Lines 522 to 541 in 6c5879f

	- in_parallel:
	- get: concourse
	passed: [rc]
	trigger: true
	- get: unit-image
	- get: version
	passed: [rc]
	trigger: true
	- get: final-version
	resource: version
	passed: [rc]
	params: {bump: final}
	- get: gdn
	passed: [rc]
	trigger: true
	- get: ci
	- get: resource-types-alpine-image
	passed: [resource-types-images]
	- get: resource-types-ubuntu-image
	passed: [resource-types-images]

to match

ci/pipelines/concourse.yml

Lines 539 to 556 in 6c5879f

	- in_parallel:
	- get: concourse
	passed: [testflight, watsjs, upgrade, downgrade]
	trigger: true
	- get: unit-image
	- get: gdn
	trigger: true
	- get: containerd
	trigger: true
	- get: runc
	trigger: true
	- get: cni
	trigger: true
	- get: ci
	- get: resource-types-alpine-image
	passed: [resource-types-images]
	- get: resource-types-ubuntu-image
	passed: [resource-types-images]

but also -

how did this happen?

what is going on with our testing that there are so many test suites labeled containerd but we're not actually adding it to our tarball? does containerd actually work with the docker image? why? what the hell?

maybe we can always build a tarball before testing (instead of baking the same dependencies into the dev image) to have more parity between our testing flows. maybe we can have some (sigh) bosh-topgun tests for containerd.

[jamieklassen]

As part of this work, please unpause https://ci.concourse-ci.org/teams/main/pipelines/release-6.3.x/jobs/bin-smoke-containerd

[aoldershaw]

The approach we're taking is to extract the dependencies directly from the dev image so we're guaranteed to be releasing with the same versions we tested against. Before, we had no passed constraints on gdn, so we could've tested with one version and released with a different one altogether!