I have a simple build chain configure in TeamCity: ``` build -> create-base-image -> -> docker publish test -> ``` I have the "On failed dependency: cancel build" option enabled. So if either `build` or `test` fails, the queued `docker publish` step will be cancelled. However if `build` fails, the `test` step continues to run all the way through and visa versa. I would like to cancel all sibling tasks if any of them fail. Or if a dependent step is cancelled (`docker publish`) I would like all currently running dependencies of that to be stopped. Someone asks the same question here: https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206926235-Cancel-other-snapshot-dependencies-if-one-dependency-fails- But I'm not sure if the linked YouTrack issue is actually solving this problem.

We are using private git repositories in Azure DevOps and I have a requirement to create code coverage report across git repositories. Our build CI/CD pipelines are using both TeamCity & Azure DevOps. I have looked at options and there is no straightforward solution to this problem. I am thinking about the following options: - using service like coveralls.io, there is an option to add private repositories; the drawback it is subscription based service - using TeamCity SonarQube plugin; It is not ideal and limited to the plugin features; I haven't tried it yet. - using custom script to query and aggregate existing code coverage metrics of last successful build in TeamCity/Azure DevOps across projects and group them by repository; Both Azure DevOps & TeamCity offer REST APIs that can be used to get the data. I still need a solution for Azure DevOps builds, however I have to admit I have not researched this properly yet. Has anyone done cross repository code coverage reporting and what approach/tools might be best?

In the .net core 2.1 project, there is a `*.csproj` file, that contains assembly information: ``` 2019.1.15341.0 2019.1.15341.0 2019.1.15341 ``` In Standard .net projects there were Properties/AssemblyInfo.cs which contained the Assembly information, but in the .net core, there is no AssemblyInfo.cs, all Assembly information are in the csproj. How can I change the Assembly Version, File Version in Assembly Info Patcher in TeamCity for the .net core projects?

These tools seem to share very similar characteristics. How complicated would it be to start using TeamCity after getting used to working on Jenkins? Are there specific concepts one needs to be aware of?

JetBrains TeamCity docker image describe build steps for already installed TeamCity. Is there any way to automate installation of TeamCity it-self? For example creating the admin account, enabling standard authentication and setting up the project?