Dear CF Devs,

The ARD working group will soon release a cloudfoundry/cf-deployment-concourse-tasks image that no longer includes an installed ginkgo CLI. [1]

We have successfully migrated most of our projects to v2 of the Ginkgo module [2], which has been out for long enough that we hope most other projects have been done the same. Therefore, we started using v2 of the ginkgo CLI as well. However, we couldn't just install the latest version of the ginkgo CLI in our docker image, as, ever since Ginkgo v2.3.0, the CLI and the local library versions are required to be in sync. This has led us to manage our ginkgo CLI version as a typical Golang tool dependency and install/use it on-demand in our projects. [3]

If your project uses the latest tag of the cloudfoundry/cf-deployment-concourse-tasks image and hasn't yet migrated to Ginkgo v2, then you may want to consider locking to an older tag of the image until you complete your Ginkgo v2 upgrade or adjust your workflows accordingly.

Best regards,

Carson Long

[1] https://github.com/cloudfoundry/cf-deployment-concourse-tasks/pull/127

[2] https://onsi.github.io/ginkgo/MIGRATING_TO_V2

[3] https://onsi.github.io/ginkgo/#recommended-continuous-integration-configuration