TC, Git branch management issue

Answered

I'll see if I can articulate this efficiently.  We have a build configuration with multiple git branches, we'll call them development, and production.  At creation time, the default branch was development.  We then changed the default branch to production.

1.) When viewing the configuration's build history, if you filter by default branch (which is production), the results show any build that was run as the default.  So in our case we see builds in the development branch AND production branch.  This seems odd, but not a big deal.

2.) If you filter by branch "production", it redirects to "default" where I'm seeing a mix of development and production builds.  This is a problem because now there is no way for me to filter the builds by production branch only while it's the default.

3.) We have another configuration that is using this one as a dependency, and the dependency is set to use production branch latest with tag "XYZ".  There is a build that matches this criteria, but it was run while development was still the default branch.  When the configuration runs, it doesn't find any matching builds.  My guess is because TC is using the same logic it does in the UI, which is redirect to default branch, and look for tag "XYZ", it's not there because production wasn't the default branch when that build was run.

Does that make sense?  Thanks

 

EDIT: We're running TeamCity Enterprise 2019.1.1 (build 66192)

- Steve

 

0
1 comment

Hi Steve, 

Thank you for the detailed description. The first point is working by design: we consider builds ever produced in the default branch important and we show you all these builds. You can even have several VCS roots in the same build configurations with different default branches, and we will show them all. The second and the third points, however, seem to be bugs.

The second point comes from the first one and is a UI bug: when you select develop or production (in your example) branches in the drop-down, you expect to see only the builds for the selected branch. However, when you select those branches, filtering by default branch gets enabled. This is confusing, I agree. I created a new bug report for the same: https://youtrack.jetbrains.com/issue/TW-64420

The third point is also a bug and indeed artifact dependencies should be resolved correctly. I also created a bug for the same: https://youtrack.jetbrains.com/issue/TW-64422

Feel free to vote for these issues.

Best regards,

Mikhail Efremov

0

Please sign in to leave a comment.