Confusing build branch list
We are using TeamCity 2023.11.4 (build 147586) with versioned settings enabled. There is some confusion about branches that are listed when starting new build (changes→Build branch→select branch). I expected to see branches from VCS root of the build but I also see branches from VCS of the versioned setting repository. I understand that I can run builds from other configurations of TeamCity/kotlin but it is confusing that those branches are mixed together. For me we should have two lists - one for VCS of the build project and one for Versioned Settings because they exists for separate purposes.
Please sign in to leave a comment.
Is your VCS root used for the versioned settings attached to the build configuration as well?
I tested it with a simple scenario, where the project has 2 VCS roots, and the build configuration has only one attached, and only the branches from the one attached VCS root are shown in the custom build dialog.
Best regards,
Anton
I have build definition with one VCS root defined that targets repository A and this build is inside TeamCity project that is versioned from repository and it has its own VCS root that targets repository B. One thing to note is that this second VCS root had branch specification for develop, pull requests and feature branches and this was the problem. Now we remove that configuration leaving only develop but when this was active those branches was visible when starting the build. Another way to filter them out was to use branch filter in build definition but it is not always easy to distinct between branches from two VCS roots and we have to do it in each branch. For now using only one branch in VCS root of versioned setting was the fix but the problem remains for me.
Could you please share the screenshots that demonstrate your settings and issue? You can upload them to https://uploads.jetbrains.com/ and share the upload ID to share them privately.
Best regards,
Anton
Upload ID: 2024_09_26_9hQEmhCm8A365rsEPuGn7D
Thank you for the provided materials. I run a couple of tests and I found the following:
1. The project has 2 VCS roots, one with sources (VCSroot1) and one for versioned settings (VCSroot2).
2. If you create a build configuration and attach only VCSroot1 to it, you will see the branches only from VCSroot1.
3. If you attach VCSroot2 to this build configuration, you will begin to see branches from both VCS roots.
4. If you then detach VCSroot2, you will still see the branches from VCSroot1 and VCSroot2.
5. However, restarting the TeamCity server will make sure that branches from VCSroot2 (since it's no longer attached) are not showing up.
I think that this is related to the cache, but please let me know if it works like this in your case.
Best regards,
Anton