Teamcity Tutorial

Introduction Installing User management in TeamCity Group management in TeamCity Setting up the projects Creating project from scratch Creating project by URL Viewing all projects, sub-projects and builds in TeamCity Project page Configuring visible projects Project configurations General settings VCS roots Report tabs Build schedules SSH keys Clean-up rules Project actions Build Configurations General settings Version control settings of a build Build steps Adding build triggers Adding failure conditions Passing parameters to build Build Configuration actions Build configuration templates Various build steps Build steps for Gradle project Build steps for Maven project Build steps for .Net project Build steps for command line Powershell runner Duplicate code finder runner Executing Selenium tests in TeamCity Running builds Viewing the build run history Environment variables in TeamCity Pinning builds Build investigations Tagging builds Configuring and Viewing artifacts of build Setting up the build agents Enable and disable build agent View build agent summary View build history of an agent viewing build agent logs Managing compatible configurations on a build agent View build runners Viewing build agent parameters Build agent pools Tracking changes Managing Build Queue Configuraing build priorities in queue Favorite builds Personal settings and tools in TeamCity Global settings in TeamCity NuGet integration in TeamCity Viewing build time in TeamCity Viewing build disk usage in TeamCity Audit and Actions in TeamCity Authentication settings in TeamCity Email server set up in TeamCity Back up builds and projects in TeamCity Importing backup in TeamCity Viewing license information Cleaning up TeamCity server Usage statistics in TeamCity Plugins in TeamCity

Build steps for gradle project in Teamcity

We have already seen all important settings of a typical build configurations. All settings in the build configurations are similar like general settings, VCS, triggers, failure conditions. What differs is the build steps. For different projects, we have to provide different build steps. In this topic, we are going to look at build steps for a gradle project in TeamCity. In build steps section, click on add a build step and select the gradle runner as shown in below image. Gradle runners needs 2 very important settings.
  • build file – By default, it is build.gradle But you can change it as per your requirement.
  • task – any valid task name. You can find the list of commonly used tasks on gradle tasks article. Here we have mentioned clean build task.
If you want to measure code coverage, you can use any of the available code coverage tool provided by IntelliJ IDEA or JaCoCo. Below image shows the sample gradle build output.
Complex problems, Simple Solutions