Failed to parse pipeline <pipeline-name> -check; null

[Manojsai katakam]

Hi , 

In our env , Config repo & yaml.config.plugin were set in place already. But when i created a pipeline as code in yaml getting below errors in log goserver log.

at com.thoughtworks.go.config.ConfigRepoPlugin.parseDirectory(ConfigRepoPlugin.java:95)

at com.thoughtworks.go.config.ConfigRepoPlugin.load(ConfigRepoPlugin.java:62)

at com.thoughtworks.go.config.GoConfigRepoConfigDataSource.onCheckoutComplete(GoConfigRepoConfigDataSource.java:160)

at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.updateConfigurationFromCheckout(ConfigMaterialUpdateListener.java:99)

at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.onMessage(ConfigMaterialUpdateListener.java:84)

at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.onMessage(ConfigMaterialUpdateListener.java:36)

at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:83)

at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:63)

at java.base/java.lang.Thread.run(Unknown Source)

Not sure if it's a syntax error or not , can anyone clarify this?

Thanks & Regards,

Manoj K

[Chad Wilson]

It sounds like a bug, or at least something that should be handled better, even if it's a configuration issue causing it.

• What GoCD version are you using?
• What configuration values have you set in your config repository and what error is displayed in the UI?
• Please also include the full error/stacktrace and relevant logs before the error. The piece you have shared looks cut off and omits important information/context.
• If there are any errors in the specific log file for the yaml config plugin (look in the logs dir), that would be good to have too.
  

-Chad

--
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+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAEbMZ9s1vJiwhftqUiN7uig-e0AKx7m06qHfeWCSf4g2x5wi4Q%40mail.gmail.com.

[Manojsai katakam]

Hi Chad, 

GoCD Version: 20.5.0 

Error displayed in UI : 

Logs in go-server :

2023-01-21 10:15:24,659 ERROR [118@MessageListener for ConfigMaterialUpdateListener] GoConfigRepoConfigDataSource:173 - Failed to parse configuration material ssh://g...@bitbucket.org/xxxxx/xxxxxx-apps.git by Plugin yaml.config.plugin

com.thoughtworks.go.plugin.access.configrepo.InvalidPartialConfigException: 

test.gocd.yaml;

1. Failed to parse pipeline splack-yaml-infra-manage; class java.lang.String cannot be cast to class java.util.Map (java.lang.String and java.util.Map are in module java.base of loader 'bootstrap')

xxxx-xxxx-agents-check.gocd.yaml;

1. Failed to parse pipeline xxxx-xxxx-agents-check; class java.lang.String cannot be cast to class java.util.Map (java.lang.String and java.util.Map are in module java.base of loader 'bootstrap')

at com.thoughtworks.go.config.ConfigRepoPlugin.parseDirectory(ConfigRepoPlugin.java:95)

at com.thoughtworks.go.config.ConfigRepoPlugin.load(ConfigRepoPlugin.java:62)

at com.thoughtworks.go.config.GoConfigRepoConfigDataSource.onCheckoutComplete(GoConfigRepoConfigDataSource.java:160)

at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.updateConfigurationFromCheckout(ConfigMaterialUpdateListener.java:99)

at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.onMessage(ConfigMaterialUpdateListener.java:84)

at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.onMessage(ConfigMaterialUpdateListener.java:36)

at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:83)

at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:63)

at java.base/java.lang.Thread.run(Unknown Source)

Thanks & Regards,

Manoj K

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAA1RwH8F2dTVdosm7Hdj3WfF0KZZReTR2srMBVRVNjw0nmTMpg%40mail.gmail.com.

[Chad Wilson]

If there is no other stacktrace log or anything in the log file specific to the yaml plugin (or possibly further up the server log) telling us the line in the plugin logic that has the ClassCastException we would probably need the YAML content of one of the pipelines, e.g "splack-yaml-infra-manage" (redacted) from test.gocd.yaml to be able to replicate the problem.

In any case, the root cause is likely a syntax error with the yaml config - likely a string value for something that should be a YAML dictionary, or some kind of indent problem or issue with a merge (<<) . You might want to consider validating the YAML locally and see if that makes it easier to find the issue, especially making sure it is valid yaml to begin with.

-Chad

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAEbMZ9vjKJQ-gTjYGw72mf0kckzUdxm3yKeg%3DCaRH6k5YoypXQ%40mail.gmail.com.