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 maven project in Teamcity

In this topic, you will learn how to set up a build steps for maven project in TeamCity. As shown in below image, you have to select runner type as Maven. Then you have to provide the goals to be executed. By default, it uses POM.xml in the root directory of the project. You may also run code coverage process along with test goal which gives report on how many classes were covered by tests. Here is the list of some of the popular maven goals that can be used.
  • test – execute tests using surefire plugin. We can also pass various parameters to maven JUnit test goal and maven testNG test goal
  • verify – executes unit tests as well as does verification provided by plugins
  • install
  • site
  • deploy
Below image shows that sample build log.
Complex problems, Simple Solutions