Teamcity DSL - Upgrade IdeaJ teamcity-configs plugin
Hi,
We have an on-premise installation of Teamcity and after upgrading from version 2023.11 to 2025.03 I want to upgrade the teamcity maven plugin in IdeaJ to match the new version but I can't find any way to do it.
I updated the version in the settings.kts file but that didn't seem to change anything.
After the teamcity server upgrade there was a problem in the DSL configuration, some files contained obsolete build step types and failed to generate the configuration.
When I tried to run the teamcity-configs:generate plugin in IdeaJ it's still on version 2023.11

I get these messages:

Downloading from jetbrains-all: https://download.jetbrains.com/teamcity-repository/org/jetbrains/teamcity/configs-dsl-kotlin-plugins-latest/1.0-SNAPSHOT/maven-metadata.xml[WARNING] Could not transfer metadata org.jetbrains.teamcity:configs-dsl-kotlin-plugins-latest:1.0-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [teamcity-server (http://192.168.10.216/app/dsl-plugins-repository, default, releases+snapshots)]
After manually finding and removing the obsolete build steps, the DSL configuration was valid and changes are applied correctly in TeamCity.
I would like to be able to upgrade the plugin so it matches the teamcity server version and validates the DSL files before I check them in to source control.
Thanks
Please sign in to leave a comment.
Hi,
Maven was unable to retrieve the artifact from your local TeamCity server because recent versions of Maven no longer support HTTP repositories by default. This is a security measure, as the HTTP protocol is considered insecure and can expose the build process to man-in-the-middle (MITM) attacks.
More information and recommended solutions can be found in the official documentation:
Maven 3.8.1 Release Notes – HTTP repository blocked.
There are two potential solutions:
- Recommended: Enable HTTPS on your TeamCity server:TeamCity HTTPS Server Configuration Guide.
- Alternative: Allow Maven to access HTTP repositories by updating your settings.xml. For instructions, (google search query).
Best Regards,
Tom
Thanks, I used the alternative method to allow access to HTTP repos and it worked.