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

Very vague error in using this resource.. #45

Closed sereeth closed 5 years ago

sereeth commented 5 years ago

We are trying to use this to set a pipeline and get an error that doesn't describe a whole lot... Is there anyway to debug this?

Logging to /tmp/concourse-pipeline-resource-out.log922228100 2018/10/15 17:37:29 exit status 1 - error: resource not found

aegershman commented 5 years ago

(Sorry for piggy-backing, but see also: [#37])

janasu71 commented 5 years ago

We have the same error, any update for "error: resource not found" ? image

marco-m commented 5 years ago

Another example of very vague error, that is also close to #37, is this:

Successfully pulled concourse/concourse-pipeline-resource@sha256:6b8a1dd2f9eba0b42e2adefc93e077f78a3014a080da9219003d5e0b712c7b76.

Logging to /tmp/concourse-pipeline-resource-out.log539779386
2019/03/05 13:32:11 exit status 1 - error: invalid configuration:
invalid jobs:
    jobs.shipit.failure[0].put.build-status refers to a resource that does not exist
    jobs.shipit.success.put.build-status refers to a resource that does not exist

I have tens of monitored pipelines, it is difficult to understand which one is the root cause (although it is possible: I can have a look at which git repos triggered the build).

bencao commented 5 years ago

Related and reported in #54, a vague error for authentication errors when a user has no permissions to read/write given pipeline:

2019/03/11 16:35:39 exit status 1 - error: oauth2: cannot fetch token: 400 Bad Request
Response:
aledegano commented 5 years ago

For reference: in PR #56 I'm proposing to output the return of the set-pipeline whether it's failing or not. I believe that could improve somehow the issue described here. Feedback is welcome!