Changes not visible in teamcity feature branch build
I have a feature branch that is branched out from master branch which is called develop. I created a new build configuration in the feature branch. Since new build configuration won't be available in the develop branch before the Pull request is merged. I added the new build configuration as dependency to an existing composite build configuration. I am able to see the build for the newly added configuration however a new committed changes are not visible in the TeamCity. What is the problem here?
Please sign in to leave a comment.
If I understand correctly, this behavior is expected.
Composite builds do not have their own checkout; their changes are aggregated only from snapshot dependencies that are fully visible and resolvable within the same versioned settings context.
The new build configuration was created only in the feature branch, so it exists only in the versioned settings of that branch. Before the pull request is merged, this build configuration does not exist in the develop branch project structure.
Although TeamCity is able to run the newly added build when the composite build is triggered from the feature branch, the calculation of the Changes tab for a composite build relies on a fully resolvable snapshot dependency graph within the same settings context.
To address this, you can try:
1. Keep the new build configuration independent in the feature branch for validation, then merge the pull request so the configuration becomes available in develop.
2. Add or activate the snapshot dependency in the composite build after the merge.
This ensures the dependency graph is consistent and allows TeamCity to correctly calculate and display changes.