Unable to change configuration after making one of the pipelines use a template

[aru...@thoughtworks.com]

Hi,

Recently I created a new pipeline in Go with a stage defined by template, also I have defined all the needed parameters in the parameter section.

However after this change, I am unable to make any configuration change even to other pipelines.

Here it cribs for SPRING_PROFILES_ACTIVE not defined, however I have defined the same in the parameters section.

Save failed. Parameter 'SPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVE' is not defined. All pipelines using this parameter directly or via a template must define it.

[Aravind SV]

Can you check the config file, and see if the parameter has been defined properly? Go seems to think that the parameter is not just SPRING_PROFILES_ACTIVE, but SPRING_PROFILES_ACTIVESPRING_PROFILES_ACTIVE... So, I think you can check the config to see if it is correct.

--
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.
For more options, visit https://groups.google.com/d/optout.

[srinivas upadhya]

I remember seeing this a long time back. Cannot seem to recollect when & why. Tried searching old bug reports etc. still no clue.

Can you give us you config so we could reproduce this scenario? Also, what release are you on?

[bd]

I am certain there's a bug here.  I have seen this in the past when I try to reference a parameter in a template, where a pipeline using that template doesn't have that parameter defined.  If you add a parameter to a template, you MUST define it on all pipelines that are using that template FIRST.  Otherwise you will get this save failure... and there's no going back unless you stop the Go server and start it again.

Every time you try to save the changes, it will append SPRING_PROFILES_ACTIVE again and again.  Stop Go Server and start it again, then update ALL pipelines using that template to have the SPRING_PROFILES_ACTIVE parameter and then try to reference that parameter in the template.

[bd]

Once you get this save error ONCE, you must restart the server, even if you go back and add the parameter to all the pipelines and try again.  I see that you commented that all pipelines have the parameter defined, but I have a hunch you may have done it after this error.  I have run into it many, many times. 

[Zabil C M]

Bug created and linked to this mail.

Please feel free to add details.

--

[Ketan Padegaonkar]

Can someone here please provide us a configuration or steps that allows us to reproduce this issue.

I've tried reproducing this, but have been unable to.

--

[Ben Davis]

1.  Create a template that has no environment variables defined.  

2.  Create two pipelines off of that template. 

3.  Add a parameter to ONE of the pipelines using that template.  

4.  Update the template and create an environment variable, and assign the parameter from the pipelines to that environment variable on the template.  When you try to save the template, it will start throwing the error.  

At this point, try going to the pipeline that doesn't have the parameter defined and try creating it.  Go back to the template and try to create the environment variable again, it should still throw the error and every time you press save, it will append the variable names and the error will get longer and longer. 

[Zabil C M]

Thanks Ben!

This is now fixed on 

 experimental release 15.2.0-2170 (05c70bb21bf9d3de8e2520a51b3a17feb8ce6d12)

 

.