Root project ID when using Maven and patches

I've got versioned settings in Kotlin and we allow users to edit in the UI.

So we get some patches.

All works fine in the UI & TeamCity compiles the DSL without issue.

But when we compile the Kotlin using Maven, all the patch files fail where the root project ID is just "RootProjectId" instead of the actual project ID on the server. ( in my case let's call that “MainProject”

So we can't compile the Kotlin using Maven - it always fails.

We get “script.content !=” errors like:

%dep.RootProjectId_NightlyBuild%

!=

%dep.MainProject_NightlyBuild%

I want to tell Maven the root project ID is “MainProject”

I tried adding properties to the pom.xml and that has not worked.

0
2 comments

Well I've solved ONE problem with patches.

It's the build step that is patched has %dep.ROOT_ID_CLASS_ID.build.vcs.number%

Changing those to $(CLASS_ID.depParamRefs["build.vcs.number"]) gets rid of the bizarre root ID problem.

The build.vcs.number is the only dep that appears to have this issue.

For eg .teamcity.build.branch is fine in a %dep.ROOT_ID_CLASS_ID.teamcity.build.branch% expression, in a patch.

And yes, you have to remove the part of the ID that is the Root Project ID before the rest of the class ID.

0

Well, I *thought* this had worked but now it's not.

0

Please sign in to leave a comment.