config repo errors (# fallowed by #)

[ashok reddy C k]

Hi Team,

We have a 60 repos  out of 17 repos have same error getting and under  config repo we can see pipelinegroup and pipelines and updated code

but errors are coming

INVALID MERGED CONFIGURATION
Number of errors: 281+

1. Error when processing params for 'echo ":start

sed -i 's/^\(\s*\)#\([^#!]\)/\1##\2/g' your-pipeline-config.yml

[Chad Wilson]

Please share the actual part of the yaml config causing the problem, the full error message for that field, and what you've tried to do to fix it. 

What was the error caused by? A GoCD version upgrade? A change to your config repos?
What steps have you specifically performed to try and fix it? What exactly happened? Did you try force-refreshing the affected config repo after fixing the pipeline definitions?

Assuming it's a change to your configs, the actual error message on UI and server logs should display enough detail to fix it.

Error when processing params for '%s' used in field '%s', # must be followed by a parameter pattern or escaped by another #

Check your config for # inside fields, especially commands or scripts and follow the advice. If it's still not clearing the errors and you think the syntax is correct try

• revert/rollback the changes to the "problem" config repo yaml back to a working state where all config repos are green and can be validated/imported.
• ensure all the errors are cleared from the UI
• then try updating/roll-forward the config repo again with the "correct" updated config with the right `##` escaping for use of `#` in a string field..

-Chad

--
You received this message because you are subscribed to the Google Groups "GoCD Users" 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 visit https://groups.google.com/d/msgid/go-cd/CAJCwbnWMTF2c%2BSpSiSGf51mCur_qXUb1bprm4bjB2b8ELUVtrQ%40mail.gmail.com.

[ashok reddy C k]

Hi Team,

we have backup AMI for one day before , we have restored it and working fine.

But regarding the issue 

we have seen in logs pipeline is not found server side, ui side we could see invalid merge due to template level some syntax issue or template under may be stage was missed due to this config repo under see error


The config repos show the same error, which is very large, spanning almost 10000 lines can't share error here.

may be developers are did made any wrong changes on template side but still surprising 60 out of 17 or 18 repos why  it was showed config error 

291+ invalid merge errors.

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

[Chad Wilson]

Impossible to tell from that description.and you did not answer any questions.

Maybe someone/something edited a server stored template which is used across 16 or 17 config repos which broke the ability for those config repos to consume/use the template. If one config repo refers to a pipeline in a second config repo, and that config repo cannot be merged, it will affect both.

Anyway, GoCD keeps an entire version controlled history of your server configuration xml in db/config.git so it should not be that difficult to correlate the time the errors started appearing to some kind of edit.

Hopefully you kept a backup of the "broken" server config and database so you can actually find out what happened, or you'll not be able to learn anything from this.

To view this discussion visit https://groups.google.com/d/msgid/go-cd/CAJCwbnXsmWhg3jV-XrccvqgFoo4SHvHvYR%2BecWhYzCZriabR3Q%40mail.gmail.com.