Teamcity plugin and feature branches
Feature branches support in teamcity plugin is misssing. Please implement this feature to make life for Team City users easier :)
We’re really happy to announce that our TeamCity plugin now has feature branches support since release 220.127.116.113 (https://www.plasticscm.com/download/releasenotes/18.104.22.1683). We encourage you to download the new plugin version and install it in your TeamCity servers to take advantage of this new feature.
There are some things you should keep in mind before the upgrade:
- Existing projects configured with Plastic SCM VCS roots will need to be reconfigured.
- There’s an issue involving the diff of moved + changed files due to limitations on TeamCity API, pending to be adressed.
- Server-side workspaces are no longer needed, so you’ll be able to safely remove them.
Thank you for your feedback!
One of the key reasons to implement GitServer was to have universal integration with all possible tools, so we stick to Git instead of having to put tons of development resources on developing and maintaining all plugins, something our competitors do not have to do (since most of them are so popular, like Git, that the vendors themselves take care of their plugins).
*Jan* any recent version supports GitServer. It was released back here: https://www.plasticscm.com/download/releasenotes/22.214.171.1249
Göran Wallgren commented
It would be better if the TeamCity plugin supported this natively.
(I hope that "SHOULD be solved with GitServer" rather means "COULD be solved with GitServer"...)
This could be an intermediate solution for some of our repositories. Our main (big) repository however needs a Plastic SCM workspace in order to build (changest number is used for the about dialog and other components, determined during build).
What is the minimum required server version for the GitServer feature?
While not a native integration, this should be solved with GitServer - https://www.plasticscm.com/gitserver/index.html
Simon Smith commented
Another request for this please. To perform a CVS trigger on the corresponding branch when a checkin occurs on any child/task/feature branch would be incredibly useful (without having to name them in advance). At the moment, we can only perform builds when our master branch changes.
Doug Cameron commented
We would LOVE this improvement!
Wow, good point. We'll check on Monday.