What is your experience with TeamCity?

Worked with TeamCity for building CI/CD pipelines. Configured Build Configurations and Projects, defined build, test, and deployment steps. Used various runners (Maven, Gradle, Docker, Command Line). Managed dependencies between builds using Snapshot and Artifact Dependencies. Set up triggers (VCS, Schedule, Finish Build). Integrated with version control systems (Git) and artifact repositories (Nexus, Artifactory). Used plugins to extend functionality. Monitored build status and analyzed error logs. Participated in setting up build agents.

Example of a build step configuration:

// Example of configuring a build step using Kotlin DSL
steps {
    maven {
        name = "Build and Test"
        goals = "clean install"
        mavenExecutable = "%env.M2_HOME%/bin/mvn" // Using environment variable
        jdkHome = "%env.JAVA_HOME%" // Specifying Java Development Kit
        runnerSettings {
            localRepository = TeamCityLocalArtifacts(RelativeArtifactPaths("m2")) // Customizing local repository
        }
    }
}

Comparison with other CI/CD tools:

Characteristic	TeamCity	Jenkins	GitLab CI/CD	CircleCI
Installation	Requires a separate server	Requires a separate server	Built into GitLab	SaaS (cloud)
Pipeline configuration	UI, Kotlin DSL, XML	Groovy (Pipeline as code)	YAML	YAML
Flexibility	High	Very high	High	High
Plugins	Many	Large number	Integrations	Job orchestration
License	Proprietary (with limits)	Open Source	Included in GitLab	Freeware (with limitations)

My main experience is with TeamCity, but I also have a general understanding of the principles of other CI/CD tools. I can apply these principles, migrate between different platforms, and choose the most suitable solution for a specific task.