What is Teamcity personal build ?

Its an ability to test your changes on a build server before actually committing anything. This concept is also refereed to as remote build.

Why do we need Personal/remote builds ?

Personal builds solves two major problems in a traditional software development.

1) Generally before committing the code , as a developer we do complete testing on our local machine to make sure that we are not introducing any problems into the build. However this is a lengthy process as we need wait for a significant time.

2) If we don’t want to wait for significant time , committing everything into build server and testing there is other approach , But this is at high risk as the developer can break the whole repo.

We can address the above two problems,if we had a flexibility of testing on build server and at the same time, no code is committed into Repo until the build is passed. Personal build is one such concept which will help us to solve this problem. It helps you to test your changes on your build server without committing anything. Once personal build is fired, developer can start working again in parallel, this can increase the productivity of the developer. if build is successful developer can push the code or else he can fire the personal build build again with the new set of changes.

As a Developer , How can i run my build using Personal build ?

1) To make use of personal builds , you are supposed to install Teamcityplugin.
( https://confluence.jetbrains.com/display/TCD9/IntelliJ+Platform+Plugin ).
2) Once plugin is installed , you need to connect to Teamcity ( Teamcity–>Login ), using team city registered user.
3) Once connected , you can trigger remote Run ( Screen-1-Remote-Run ).
4) As a next step you will see different projects and builds available with Teamcity, select the required build configuration.
5) Along with that, in the same screen, click on customize icon present on the top, this options helps to set environment variables.
6) Then click on ok, with all the local changes a patch is generated and pushed to team city ,build ( docker image ) then gets triggered at Teamcity along with all the latest changes on Git.
7) Plugin provides clear build status at the bottom of the IDE. (Screen-4-IDE_Console)
8) If build is succeeded, you can see success message in IDE console.
9) If build is failed, you can see the message in IDE console. Along with this,Teamcity will send a email notification to the team city logged in user used at step-2