gocd: Error scheduling pipeline, no compatible revisions
Either since upgrading to 15.2 or since removing one of the dependencies my downstream pipelines no longer automatically trigger, due to the following error:
Error while scheduling pipeline: DownstreamPipeline as no compatible revisions was identified. [Jul-28 12:32:34]
Failed resolution of pipeline DownstreamPipeline : Cause : No valid revisions found for the upstream dependency: DependencyMaterialConfig{pipelineName='UpstreamPipeline', stageName='release'}
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 15 (4 by maintainers)
I think I found the issue. PipelineA actually has quite an intricate upstream mapping. It turns out that 1 of the git materials is used in 2 pipelines (e.g. pipelineX and pipelineY) with different triggers (1 is manual, the other on a weekly cron schedule). Both of these pipelines are mapped in upstreams somewhere (2 or 3 degrees up from pipelineA) and so there is a discrepency between the versions of git used in X and Y and ends with the incompatible build.
A great feature in Go would be to somehow disable dependency validation in the upstream mapping on certain pipelines.