teamcity | Python package providing access to the JetBrains TeamCity | Plugin library

As one of the maintainers of GitVersion, I'm obviously biased, but since you're asking how to use GitVersion to implement a "best practice for automated software release", I'm going to unashamedly give you a textual description of a talk I've done on how I prefer to version and release software with GitVersion, TeamCity and Octopus Deploy.

The first thing you should figure out is what kind of developer workflow you want for your software. GitVersion supports Git Flow and many simplified variants of it, and GitHub Flow (as well as many other trunk based development flows). Which workflow you should choose depends on what type of software you are developing, your team and most importantly; your personal preference.

Once you have chosen your workflow, you can configure which mode GitVersion should operate under.

GitVersion works by calculating a version number from your Git repository. This means that you should not commit a version number to Git in any shape or form. Not within a package.json, pom.xml, .csproj, or any other build- or project-related file that often mandates the existence of a version number.

Instead, you should allow GitVersion to produce a version number based on the Git history, using the currently checked out commit as its starting point, and searching through the parents and their tags to calculate an appropriate version number for the current commit. This version number can then be used in any way you want in your build pipeline. You can, for instance, write GitVersion's FullSemVer variable to package.json by executing the following command:

There is a fork of JSch which has support for modern algorithms and should be fairly robust. I know of at least one major organization using it against GitHub with success.

However, note that it disables RSA with SHA-1 support by default, because it's insecure (which is why GitHub is phasing it out), so if you need to work with sites that don't support anything else (e.g., Azure DevOps at the moment), you'll need to set some configuration accordingly.

You may also be able to use Apache Mina in conjunction with JGit. The 5.13 release of JGit supports Mina 2.7.0, which should support modern algorithms.

I'm working with a similar configuration: a FastAPI application that uses Firebase Emulator suite to run pytest cases agains. Perhaps you will find these build steps suitable for your needs too. I get both test reports and coverage using all the built-in runners.

Reading the TeamCity On-Premise documentation, I found that running a build step command within a docker container will pick up TEAMCITY_DOCKER_NETWORK env var if previous steps ran docker-compose. This variable is then passed to your build step that runs in docker via --network flag, allowing you to communicate with services started in docker-compose.yml.

Three steps are required to get this working (please ignore numbering in the screenshots, I also have other steps configured):

1. Using Docker runner, build your container where you will run pytest. Here I'm using the %build-counter% to give it a unique tag.

1. Using Docker Compose runner, bring up other services that your tests rely on (postgresql service in your case). I am using teamcity-services.yml here because docker-compose.yml is already used by my team for local development.

1. Using Python runner, run Pytest within your container that was build in step 1. I use suggested teamcity-messages and coverage.py, which get installed using pip install inside the container before executing pytest. My container already has pytest installed, if you look through "Show advanced options" there's a checkbox that will let you "Autoinstall the tool on command run" but I haven't tried it out.

Contents of my teamcity-services.yml, exposing endpoints that my app uses when running pytest.

Read carefully and understand at least part of GitVerson docs (paragraphs 1+2)

The shortest possible extraction

GitVersion will increment the metadata for each build so you can tell builds apart. For example, 1.0.0+5 followed by 1.0.0+6. It is important to note that build metadata is not part of the semantic version; it is just metadata!

The %teamcity.build.triggeredBy% parameter is not populated with the user that pushed the changes to git - according to the docs, it's simply:

Human-friendly description of how the build was triggered

Thus, the value Git indicates that the build was triggered by the fact that new commits were pushed to the Git repository, which is configured as VCSRoot for this project.

There is no easy way to obtain the information you need. There are a couple of options outlined in this post:

• use TeamCity REST API
• use Git command-line tool

Upgrade your nuget packages to the latest and it should fix your problem. I think you need 2.2.8 for MSTest.TestAdapter and TestFramework.

It seems like you're looking for the reverse.dep.* pattern, which is best described in the official documentation.

Quoting the docs:

It is possible to redefine build parameters in the snapshot-dependency builds when the current build starts. For example, build configuration A depends on B and B depends on C; on triggering, A can change any parameter used in B or C.

It looks like this is your case:

To change a parameter in all dependencies at once, use a wildcard: reverse.dep.*.

Anyway, I would encourage you to read the whole article to get thorough understanding of the subject and choose the most suitable option.

While the python:3.8.0 image has a windows architecture available, it looks like it's pulling the linux version from that tag. You can test this by adding the command uname -srm to the first line of your test scripts.

I wasn't able to get a windows docker image for python running on a shared runner, but I was able to install python 3.8 on a runner with the following minimal .gitlab-ci.yml:

This can be set at the .NET build step in Teamcity. There is a field for Command Line Parameters in which you can include