Hi Pavel, thanks for your reply. It's not really important _when_ to block, but let me clarify it a bit.

I'm trying to automate part of our deployment process and I was considering to move a step which requires user intervention on TeamCity as well.

As per our actual deployment process user intervention in required to confirm closing issue tracker points upon releasing a software. At the moment whoever is doing the release is prompted by a desktop application GUI where he can close tickets. Moving that step on TeamCity would mean integrating the API used to interact with the issue tracker with a TeamCity plugin which shows either a page or a user interface widget where the user can perform the same task. Once the user completes the blocking task the build can proceed.

I'm evaluating the feasibility of such a plugin and looking for advice.

Thanks a lot, I will look at the docs then. Since I'm a noob in Java is there any special environment requirements to build a TC plugin or an IDE like IntelliJ IDEA, Eclipse or NetBeans goes?

Hi Pavel, I have started playing with the TC API to try creating a plugin, and I'm wondering if there's way to replace entirely how TC reponds to the RUN button for build configurations, since that's what I'm trying to achieve.

I understand. Do you think there is any way then I can show a page to the user to which he has to respond to by filling-in some data before letting the build continue?

Hi Yegor, let me explain briefly.

I am trying to integrate TC into our current release system. At the moment we use some client applications to do that, and they require user intervention at the beginning of the process. This is needed to select issue tracker items to close, choosing which version to release, and quite some other stuff which integrates with some databases and services. I am evaluating whether it is doable to move this stuff on TC by extending the user interface in the first place.

In this scenario I would need to present a custom UI when a build is started which prompts for some information from the user, backed by a web service which interacts with our current system  and then continues the build.