concourse / concourse-pipeline-resource

!!! use the `set_pipeline` step instead !!!
https://concourse-ci.org/jobs.html#schema.step.set-pipeline-step.set_pipeline
MIT License
76 stars 42 forks source link

'tag 3' concourse-pipeline-resource Docker image cannot log into Concourse v3.14.1 #74

Closed pears0 closed 4 years ago

pears0 commented 4 years ago

Same as the issue back in August 2018 with the latest tag, accept it is now happening with tag 3 which was supposed to be the supported tag version for concourse 3.14:

https://github.com/concourse/concourse-pipeline-resource/issues/41

xtremerui commented 4 years ago

Thx for reporting this. The change is done in our CI

https://github.com/concourse/ci/blob/5c2f5d23f348156d837626f726ffb8e1ad12e388/pipelines/resources/template.jsonnet#L126-L128

When we bumped the major version to 3.0.0 2 weeks ago it also updated tag 3 and tag 3.0 with latest image that has fly 6.1. We didn't realize there was an image with tag 3 that manually built for #41. Sry about this!

pears0 commented 4 years ago

Thank you for jumping on it so quickly. Any idea when we can expect the rebuilt image to be up in the docker image store?

xtremerui commented 4 years ago

@pears0 i have pushed the rebuildt image with tag 3. Its fly version is 3.14.1. Let me know if it solve your problem. Thx!

pears0 commented 4 years ago

@pears0 i have pushed the rebuildt image with tag 3. Its fly version is 3.14.1. Let me know if it solve your problem. Thx!

I see the image has changed, but we now have the json error from the original bug report in Aug 18:

Logging to /tmp/concourse-pipeline-resource-out.log046856176 2020/05/28 06:45:36 exit status 1 - error: unknown flag `json'

xtremerui commented 4 years ago

ahh, just pushed another image with the right version. It should be back to what it was now.

pears0 commented 4 years ago

Thank you. I can now confirm that this is all working for us again.