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

Fails in 6.1.0 #73

Open pikesley opened 4 years ago

pikesley commented 4 years ago

With reference to #71 I am now testing Concourse 6.1.0. I have removed the tag so I'm using the latest version of this resource, but now in the check I get:

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?

pikesley commented 4 years ago

And I cannot hijack the container to inspect those logs:

↳ fly -t six hijack --check pipeline/existing-pipelines
error: 400 Bad Request websocket: bad handshake

This is running on a GKE cluster with nginx ingress

prein commented 3 years ago

For the "400 Bad Request websocket" error, try enabling websocket support in ingress controller, by adding following annotation to your ingress (for example via concourse helm chart values if you are installing Concourse using Helm)

web:
  ingress:
    annotations:
      nginx.org/websocket-services: concourse-web