Closed neumayer closed 5 years ago
Never mind, I think it is one of the included images, is it. In that case it was one worker that wasn't updated yet and therefore had the old binary.
@neumayer this breaks our pipelines too and i'm sure all our workers were updated to v4.0.0
it could be because the image of this resource hasn't been built with the new fly binary. its pipeline is actually paused right now. https://ci.concourse-ci.org/teams/resources/pipelines/concourse-pipeline
Hehe, so I reopen :-)
Still doesn't work. Push button please!!! )
We discovered that we fell in the opposite direction because our pipeline still uses 3.x version of Concourse. When the new version of this resource was pushed to dockerhub it overwrote latest and the previous version was lost. This means that this resource can no longer be used with older versions of fly. Is there a final stable release of this docker image for 3.x fly? If so can it please be pushed to dockerhub under a different tag for compatibility with older deployments?
It's pushed now and available as latest
and also 4.0.0
. Thanks for waiting!
Hi.
https://hub.docker.com/r/concourse/concourse-pipeline-resource/tags/
It breaks my concourse pipeline setup because the fly binary in the container is still 3.14.1. If I understood this correctly.