Teamcity does not pick up the setting.kts change

Hi team,

I added a functional testing build config into setting.kts to one of my c++ projects. 

Then I created a branch of the c++ project to test the setting.tks change out,

but seems the change was not picked up by the build.
I can see the setting.tks change already been included into the build's “change” tab,

but in the build log there is no build steps for the “functional testing”.

Would please anyone help and show some direction for investigation please? 

Regards,

Louisa

0
7 comments
Hi Louisa,

Could you provide more details on your versioned settings set up?
Is your Kotling DSL TeamCity project stored in the same VCS root as your C++ project itself?
Please also share the screenshot of versioned settings. You can upload it to https://uploads.jetbrains.com/ and share the upload ID.

Best regards,
Anton
0

Hi Anton,

Thank you for the reply!

My Kotling DSL TeamCity project and C++ project are stored in github but in different repos.

versioned settings Upload ID: 2024_10_23_aHRBuFo1cQz9ZTp2uWckNc

Regards,

Louisa
 

0

Hi Anton and support team,

Could I please get some reply/help on this one? This had blocked our CI project, thanks.

Regards,

Louisa

0
Dear Louisa,

Sorry for the wait.
It looks like your TeamCity server was updated some time ago, but the versioned settings were not. At least the behavior and error look like it. Please check https://www.jetbrains.com/help/teamcity/2024.07/storing-project-settings-in-version-control.html#Enabling+Versioned+Settings+after+TeamCity+Upgrade.
And there is also a link in the error message (DSL scripts should be updated), please check where it leads to.

Best regards,
Anton
0

 Hi Anton,

Thank you and just an update, we cleared the errors by updating the DSL version. And to sync the settings.kts and TC UI, since we did some change to the vcsroots, we had to detach the vcsroots from UI, then comment out “add(RelativeId(xx))” in settings.kts to let vcsRoot to be created, then adding them back again in settings.kts with the new vcsrootIDs. (note: above steps might not be the full step but to give some ideas how to be able to fix it). 

The issue had been fixed as per my step above. But I was expecting the changes between settings.kts/ TC UI, also the vcsroot change(we changed the repo) might be able to sync themselves, but seems there is some trick to be done to make this happen. Let me know if this is expected or I might miss something? thanks.

Regards,

Louisa

0
Dear Louisa,

I'm glad to hear that the issue was resolved.
It looks to me that the TeamCity was updated, without the DSL version being updated, so it couldn't sync. Then, the VCS root was changed, which put the settings out of sync. That's why these steps you did were needed to fix the synchronization issue.
Please let me know if there is anything else I can help you with.

Best regards,
Anton
0

Please sign in to leave a comment.