Better explanation of "built from incompatible revisions" on VSM

[ketan]

Issue Type

• Documentation Report

Summary

The VSM currently simply says "built from incompatible revisions" with no explanation of what that really means. It might be useful to document this somewhere and possibly link to the documentation when the warning appears on the VSM.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.

[chris-gillatt]

I realise this is an old closed issue, but I thought I'd add hint for others. You get this message when a pipeline has been force pushed when an upstream pipeline is paused or failed. As a result, the pipeline is able to be built from incompatible revisions. This usually occurs with complex VSMs, where two or more upstream pipeline dependencies depend on a common ancestor which is unable to build. The way to resolve it is manual.

1. Open up the VSM for the affected pipeline
2. Open up each of the upstream pipelines one at a time, and ensure that they are unpaused and passing.

Once you hit the one blocking a compatible build for your affected pipeline, the warning will disappear and a build will trigger (assuming the default pipeline settings).