"Editing of the build configuration settings is disabled." on all configurations

Hi Matt,

This happens when versioned settings are activated for the project/projects, as having them in VCS disables the option to edit them through the UI. While we are working on being able to edit the UI and having them on the VCS, it's not an option so far.

If it's not the case, it would be useful if you could share a screenshot of the banner and check the teamcity-server.log for the server restart and see if there is any error message with a stacktrace you could share.

Yeah that solved it. I never knew that synchronising to VCS means you can no longer use the web interface to edit configurations.

I think that should be made really clear when someone goes to use synchronisation because not getting that means a lot of head scratching and log searching to figure out why you suddenly can't edit stuff. I spent ages trying to find out what happened, and it was expected behaviour for the software! Very frustrating experience!

Thanks for your help though

Hi Matt,

Are you using an old release? Because recent releases have as part of the banner text an indication that visual editing is disabled because versioned settings are enabled.

There's no banner anywhere that says "Editing of the build configuration settings is disabled, reason: versioned settings use context parameters" when you start using them Denis Lapuente why should using context params prevent me from using the UI completely??

Just recompile the same as if it's from VCS. isn't that how you've enabled editing from both anyways? it submits a patch and then reloads the DSL?

Also on top of that, disabling the UI completely takes away the ability for users to LEARN what they should do in kotlin THROUGH the UI. just refuse to SAVE the changes.

Hello Sampson!

There are specific cases where patch for UI change may not be created easily; please refer to the feature request on allowing the UI changes with context parameters for the details. It also describes a workaround, but you have to be wary of the corner cases mentioned in the description. Please feel free to vote or comment on the request as you see fit. 

In regards to learning DSL via example; yes, I agree that blocking UI changes takes that option away. You may use

/app/dsl-documentation/index.html

endpoint to access the DSL documentation with examples and model reference, though (please find an example on our publicly available instance). Alternatively, you may use a sandbox project to test out the changes there before making a commit to your main repo. 

Please let me know if this helps.