GoCD reporting multiple "no compatible revisions"

[Kurt Yoder]

All,

Recently my GoCD web UI started showing multiple errors "no compatible revisions". The error text (with pipeline names changed to protect the innocent) is:

Failed resolution of pipeline ThePipeline : Cause : No valid revisions found for the upstream dependency: DependencyMaterialConfig{pipelineName='TheUpstreamPipeline', stageName='clean'}

Here's a screenshot:

Of course, once I get these, ThePipeline no longer automatically builds. Yet I can manually kick off ThePipeline and it includes the upstream dependency TheUpstreamPipeline. The web UI errors disappear with ThePipeline is building. Then once it's done, it once again starts generating errors on the web UI.

How can I get rid of these errors, and get ThePipeline to resume its automatic builds?

Thanks,

-Kurt

[srinivas upadhya]

Thats fan-in feature:
http://www.go.cd/documentation/user/current/advanced_usage/fan_in.html

http://www.go.cd/documentation/developer/5/5.2.html

[Kurt Yoder]

Hi Srinivas,

Thanks for replying. I read through the documentation links you provided and gained an even greater appreciation for GoCD fan-in. I sure am glad I don't have to manually set up fan-in!

Within the docs, I found the section "General reasons for auto-trigger downstream pipelines to not trigger (with errors)". Is this what I should focus on?

I am having trouble deriving specific troubleshooting steps from that section so that I can diagnose and fix the error. I will try looking at the upstream pipeline that is mentioned in the error message, to see if one of the reasons makes sense to me in that context. If I manage to fix it, I will report back with my resolution information.

-Kurt

[Kurt Yoder]

Great! Thanks so much for your help and suggestions. I will check it out and report back.

-Kurt

On Oct 20, 2014, at 11:50 AM, srinivas upadhya <srinivas...@gmail.com> wrote:

> Yes. You are looking at the right section. Its usually the 3rd point there (change in materials of upstream pipeline)
>
> I have tried hard to automate the resolution process. Its non trivial and always end up postponing it :(
>
> But.. we have internal apis to debug any fan-in issue. Send in the output of following URLs if you need further help.
> https://<go-server>/go/api/fanin/<pipeline-name>
> https://<go-server>/go/api/fanin_trace/<pipeline-name>
>
> Note: Please sanitize data before posting.

[srinivas upadhya]