reverse dependency parameters can only be used under special conditions: The reverse.dep. parameters are processed on queuing of the build where the parameters are defined. As the parameter's values should be known at that stage, they can only be defined either as build configuration parameters or in the custom build dialog. Setting the parameter during the build has no effect.
I am trying to pass parameters between Build A and Build B. But I need the value of my parameter of my Build A in Build B, I need to update dynamically. The value is updated depending on the result of BUild A, so that value will always be changing. I need to use it in VCS settings in: Branch Default.
A couple comments, first, you can use "dep.<build_id>.param_name" to use "param_name" from the build with ID <build_id>. So, if B depends on A, you can set B to use dep.A_id.build.branch, for example, to reference its branch.
This said, default branch is kind of a special setting. While it works just like each other, it's often misinterpreted how TeamCity uses the VCS Roots and branches leading to this not working as you would expect. Could you expand on what exactly you are trying to achieve with this parameter reference?
I am experiencing similar issue with the new override.dep. I have parameters that set branches. The chain checkouts wrong branches before the start and the jobs that checkout the repositories get the repositories with wrong branches.
The override.dep.* parameters appear correctly in the dependency build’s parameter list but are not applied to its VCS checkout. TeamCity still uses the branch or checkout rules that were in effect before the override. This behavior matches TW-101181.Please vote for the issue and watch it for updates.
According to the issue description, reverse.dep.*. correctly sets teamcity.build.branch on a dependency. We have not verified this workaround in your environment, but please try replacing override.dep.*. with reverse.dep.*. for the affected branch or checkout-rule parameter and let us know the result.
If you use Kotlin DSL with Versioned Settings synchronization enabled, please also check TW-85752, which describes reverse.dep..teamcity.build.branch being ignored in that setup.
Hi Stefan,
What are you trying to do? As you can see here: https://confluence.jetbrains.com/display/TCD10/Predefined+Build+Parameters#PredefinedBuildParameters-OverridingDependenciesProperties
reverse dependency parameters can only be used under special conditions:
The
reverse.dep.parameters are processed on queuing of the build where the parameters are defined. As the parameter's values should be known at that stage, they can only be defined either as build configuration parameters or in the custom build dialog. Setting the parameter during the build has no effect.Hi, sorry. This was meant to be a support ticket but I could not find a way to delete my post but only edit it to empty.
Hi Denis,
I am trying to pass parameters between Build A and Build B. But I need the value of my parameter of my Build A in Build B, I need to update dynamically. The value is updated depending on the result of BUild A, so that value will always be changing. I need to use it in VCS settings in: Branch Default.
Thanks
Hi Leslie,
A couple comments, first, you can use "dep.<build_id>.param_name" to use "param_name" from the build with ID <build_id>. So, if B depends on A, you can set B to use dep.A_id.build.branch, for example, to reference its branch.
This said, default branch is kind of a special setting. While it works just like each other, it's often misinterpreted how TeamCity uses the VCS Roots and branches leading to this not working as you would expect. Could you expand on what exactly you are trying to achieve with this parameter reference?
I am experiencing similar issue with the new override.dep. I have parameters that set branches. The chain checkouts wrong branches before the start and the jobs that checkout the repositories get the repositories with wrong branches.
The
override.dep.*parameters appear correctly in the dependency build’s parameter list but are not applied to its VCS checkout. TeamCity still uses the branch or checkout rules that were in effect before the override. This behavior matches TW-101181.Please vote for the issue and watch it for updates.According to the issue description,
reverse.dep.*. correctly setsteamcity.build.branchon a dependency. We have not verified this workaround in your environment, but please try replacingoverride.dep.*. withreverse.dep.*. for the affected branch or checkout-rule parameter and let us know the result.If you use Kotlin DSL with Versioned Settings synchronization enabled, please also check TW-85752, which describes
reverse.dep..teamcity.build.branchbeing ignored in that setup.Yes, `reverse.dep` works fine, we just wanted to switch to `override.dep`. We will wait and watch the ticket. Thank you.