Missing changes when triggering a personal build from virtual stream
Hello,
We are having a problem when running personal builds from virtual streams and I would like to know whether it is a problem with our setup or a limitation of TeamCity (we are on version 2021.2.2). The changes from the virtual stream submitted to the personal build are missing from the final build
We have the following setup:
* project-mainline (mainline stream)
* project-mainline-feature-1 (virtual stream)
* project-mainline-feature-2 (virtual stream)
We have a build configuration that developers use to run personal builds on project-mainline. The setup of the VCS root is as follows:
If I checkout project-mainline and trigger a personal build, my changes are in the build.
If I checkout project-mainline-feature-1 and trigger a personal build using the same build configuration, my changes are not in the build.
I was expecting the "Enable feature branches support" option to handle this use case. Am I mistaken? Should I have a separate VCS root & build configuration per virtual stream?
Thank you,
Clement
Please sign in to leave a comment.
Hello Clement,
It seems that you are experiencing the following issue:
https://youtrack.jetbrains.com/issue/TW-29199/Remote-run-on-git-branch-runs-on-default-branch
As mentioned in the comments, you can try the following workaround:
Note: the branch itself must be visible to TeamCity.
We also recommend you to follow and vote on the issue above.
Thank you,
Guilherme
Hi,
I came across this thread and I would like to mention that the behavior of the workaround is different than what might have been intended in the original post.
While the solution work, TeamCity will create a different workspace for each stream instead of reusing the same one, which is a big difference. It would be nice to have virtual streams to work as any other stream using the default behavior of the feature stream support. Or at least, to have a way to say we want to reuse the workspace.
That's my 2 cents on that topic.