Hi Vamshi, Please keep in mind that the subsequent pipeline is only triggered after a successful execution the one that it depends on.
I'm afraid that I would need more details to be able to help you out. Can you provide more information? Best Regards, Diogo Oliveira segunda-feira, 10 de Abril de 2017 às 09:49:06 UTC+1, Vamshi krishna escreveu: > > I'm using the GoCd 16.12 and recently migrated our source control and > updated the material url to the new source control in the config xml. after > updating the config xml, the go pipeline got triggered and the subsequent > pipeline isn't getting triggered and the following error being thrown. > *Error while scheduling pipeline: <pipeline_name> as no compatible > revisions were identified.* > *Failed resolution of pipeline <pipeline_name> : Cause : No valid > revisions found for the upstream dependency: > DependencyMaterialConfig{pipelineName='<pipeline_name>', > stageName='<stage_name>'}* > What is the fix for this ? > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.