Fan-in is a feature in Go that tries to resolve multiple pipelines depending on the same SCM down to a common revision before triggering a dependent downstream pipeline. This is done in order to avoid wasted builds. You can find more information on this feature in in our documentation and on our website.
The error that you noticed in the warnings & errors box indicated that Go could not resolve the revision using the fan-in feature and hence has to fall back on the old way of pipeline resolution. This would basically result in an extra build for your CI pipeline which is why you see that the pipeline seems to work fine. This is not really an error state and hence can be ignored for now.
Comments
1 comment
Hi Paul,
Fan-in is a feature in Go that tries to resolve multiple pipelines depending on the same SCM down to a common revision before triggering a dependent downstream pipeline. This is done in order to avoid wasted builds. You can find more information on this feature in in our documentation and on our website.
The error that you noticed in the warnings & errors box indicated that Go could not resolve the revision using the fan-in feature and hence has to fall back on the old way of pipeline resolution. This would basically result in an extra build for your CI pipeline which is why you see that the pipeline seems to work fine. This is not really an error state and hence can be ignored for now.
Cheers,
Jyoti
Please sign in to leave a comment.