Project Overview page shows git tag names - stopped working

Answered

Builds that are built from git tags, show the tag name in the Project Overview page.  Recently the tag names have not been appearing in the Project Overview page.  In theory, I have not changed anything, but I am guessing that I must have.  What is TC looking at to show the tag name, the only place is the Version Control:

 

This is the only match that I can see.

 

5 comments
Comment actions Permalink

Hello Jon,

Just for my understanding - is the issue you are experiencing related to the new tags not appearing among the branches viable for build (e.g. under Active branches dropdown):
Or do the builds based on Git tag not show up on the overview?
The overview page will show the active branches and the last build of these branches. If there were no builds or changes in 7 days (by default) on a certain branch or tag, it will not appear on the overview tab.

If new tags do not appear on the TeamCity side, please check that "Enable to use tags" option is active and corresponding specification is available in VCS root settings:

 

0
Comment actions Permalink

Fedor,

I should have said the Projects page.  The v2.0.1.8 is a git tag that the config was built from.  It is a great indicator of what tag we are on.  In other builds, similar to the one shown the tag is no longer displayed and I am not sure how TC displays it other than from the git tag that was in my first post.

 

0
Comment actions Permalink

Hello Jon,

I deeply apologize for another delay with response here. Am I correct to assume that the tag you have highlighted on a screenshot is not a name of branch based on Git tag, but rather a tag itself (which has been populated by source labeling feature)? If so, this issue may be related for your case:

https://youtrack.jetbrains.com/issue/TW-65317

Could you please:
1) confirm what does Active Branches dropdown has on e.g. "Developer builds run on every checkin" build configuration (or on any other configuration that used to show tag but does not do it now)?
2) let me know if you previously had "Enable to use tags" on branch specification enabled?

0
Comment actions Permalink

So we have over 20 build configurations that I have setup, but I have not stayed up with the terminology or features.  With that said I will try to answer your questions.

So v2.0.1.8 is actually a git tag and not a branch.

1) I don't know where the Active Branches dropdown is.  I think it normally shows up on the Projects page, as you can see none of our build configurations have a popup.  If you can tell me exactly which page holds the Active Branches dropdown, I will try to answer your question.

2) No, I don't believe we ever had "Enable to use tags" enabled.

We are running 2019.2.2, which was noted in the Issue you linked.  I might try to update to 2020.1.

TC has become so powerful, but with all the features and flexibility it has been hard to keep up.  In theory, I think it should be easy to answer to how to get the v2.0.1.8 to show up in the x column, I don't even know what to call that column on the main projects page.  I do appreciate all your time in helping me, but I am not sure we are moving forward on the issue.

0
Comment actions Permalink

Hello Jon,

Regarding the Active Branches dropdown - apologies, should have mentioned that from the start. You may find it here (on the Build Configuration overview page):


Do you have v2.0.1.8 on that dropdown for the configuration which lists that tag on the overview page?
The case looks fairly weird; please let me explain further. Normally, the column in question will list the branch which has been used for build under this configuration recently. Normally, we do not deal with tags when loading branches from VCS (but we provide ability to set them automatically). However, if "Enable to use tags" option is on, tags will be treated as buildable "branches" on the TeamCity side (and, therefore, builds ran on the "branches" based on tags will show the tags on the overview page). You have confirmed, though, that the tag option was never on, so the tag should never have appeared on the overview page either in this case. The only case when this could have happened would be when a branch named in the same convention as tag (e.g. refs/heads/v.2.0.1.9) falls under the branch specification - but again, you have confirmed that we deal with a tag here, not a branch. 

One more possible explanation is tied to the usage of teamcity.build.branch build parameter (https://www.jetbrains.com/help/teamcity/predefined-build-parameters.html#PredefinedBuildParameters-Branch-RelatedParameters). It may be supplied to the build configuration so to change the label (and correspondingly the value you see on the column in question on the overview tab); chances are that you had this parameter set automatically earlier, but either it was removed or a value ceased to be populated. Please let me illustrate how it works:


Note the test_tag on the Branch column. I do not have neither branch nor tag under this name, yet it will appear here and on the Project Overview page as long as it is considered active. That being said, we do not recommend this method because of the downsides (this may possibly interfere with dependencies or triggers logic). You could check internally if this logic was in use recently, though, as this would probably explain the changes in behavior.

Regarding the upgrade; while beneficial, it will not change the behavior (as the TW-65317 was not reproduced yet and, therefore, has no described scope/ready fix). 
I do hope the above will be helpful; please do not hesitate to reach out and I will try to assist further.

0

Please sign in to leave a comment.