Teamcity Build Feature (Automerge) does not consider overriden parameters via REST
We have an automerge step in Teamcity with a configuration parameter that we override when we start the build via rest api. The Teamcity UI also shows the correct (overriden) value in bold in the parameters section. However the build feature Automerge resolves the variable and uses the default value (that is configured in Teamcity) instead and ignores the overriden value.
Is this expected behaviour? Is there a workaround for triggering a merge on Teamcity via REST API? (we are using server checkout)?
Please sign in to leave a comment.
May I ask you to create an issue in our tracker here: https://youtrack.jetbrains.com/issues/TW
Are you overwriting the parameter via the REST request or is it being overwritten through the build process itself?
We're setting the parameter via the REST request, like this:
<build branchName="..."><tags><tag name=".teamcity.star" private="true"><owner username="${env:USERNAME}"/></tag></tags><buildType id="..." /><properties><property name="targetBranch" value="..."/></properties></build>
The property "%targetBranch%" is used for the "Automatic merge" build feature, as the "Merge into branch" value. When viewing a concrete build's "Parameters" view, the right value (passed via the REST request) is shown (in bold). However, the build feature always uses the original default value of the variable.
https://youtrack.jetbrains.com/issue/TW-56204