search

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

Fly version mismatch #71

Closed pikesley closed 4 years ago

pikesley commented 4 years ago

Hi

Two of my pipelines (in my 5.8.0 Concourse deployment) use this resource, and they suddenly started failing their checks this morning with

fly version (6.1.0) is out of sync with the target (5.8.0). to sync up, run the following:

At the time of writing, the last successful runs were 22 hours ago, and the new version of this resource arrived on Dockerhub 21 hours ago, which suggests that something's broken in that release. Has anybody else been hit by this and maybe found a workaround?

Thanks

Sam

vito commented 4 years ago

See https://github.com/concourse/concourse-pipeline-resource/issues/70

Please pin the resource to tag: 2 until you've upgraded to v6.1.0, or switch to the set_pipeline step if you can.

pikesley commented 4 years ago

Thanks, I tried this and it worked!

We're testing Concourse 6 next week...

pikesley commented 4 years ago

I am now testing Concourse 6.1.0, I have removed the tag so I'm getting the latest version of this resource, but now in the check I see:

run check step: run check step: check: resource script '/opt/resource/check []' failed: exit status 1

stderr:
Logging to /tmp/concourse-pipeline-resource-check.log692886880
2020/05/21 15:06:04 exit status 1 - error: resource not found

Am I doing something dumb?