Child pages
  • Faradi 7.0 EAP (build 21075) Release Notes
Skip to end of metadata
Go to start of metadata


A long-standing feature request to allow build configuration editing via REST has finally been implemented.
Now you can get complete settings of build configuration or a template via REST and can also change them.
You can also create and delete build configurations, projects and VCS roots.

Here is an example of how to get build configuration steps:

Save individual step details into a file:

And create a new step (a copy of the saved one):

REST API has "/app/rest/application.wadl" since the very beginning, but it now got XML schema attached and will hopefully get some more inline comments soon.

We would appreciate if you could try the updated REST API and let us know about any issues or suggestions that you might have.
It can still change in final 7.0, so do not yet finalize your code, but rather let us know what we can enhance.

If you already use REST API please note that the protocol version has changed.


We introduced dependencies tab in previous EAP builds. It shows all build chains of a particular configuration or a build.

With this EAP you can have much more control over your build chains. As you can see from screenshot you can run dependent parts of the chain right from this page.
In this case TeamCity will use the same revision for dependent builds and will attach new build to the existing chain. Thus, it works quite similar to a pipeline.
If you reached some stage during release process and want to prolong pipeline to some further stage, now you can do it easily.

During release process some parts of pipeline can fail because of reasons not depending on source code. For example, deployment task can fail, if servlet container was stopped.
In such cases it is important to have ability to rerun some part of the chain. This action is also available, note that "rerun" build will use revisions of the chain.

Additionally, if you want to rebuild several dependencies you can do it from custom build dialog:


TeamCity now uses Java based back-end for handling NuGet feeds.
This should simplify setup of NuGet in TeamCity and as an additional benefit you can use TeamCity NuGet feed feature if server is installed on Unix.


Both Maven2 and Maven3 are now bundled with TeamCity. You can choose required version of Maven on the Maven runner page.
Additionally you can instruct Maven runner to use unique local artifacts repository for the builds of build configuration.

Ruby environment configurator

The long standing bug with non functional Ruby environment configurator ( has now been fixed.
If you've faced it, please try the fix.

Additionally, agent now detects presence of RVM on machine and reports rvm_path environment variable with path to RVM.
This way you can easily configure your build configurations to run on agents where RVM is installed.
Enabling of Ruby environment configurator will add this requirement automatically.

Other changes

  • new filter on current problems allows to hide assigned problems
  • first failed in section shown for stacktrace has been improved
  • option to show changes from snapshot dependencies moved to build configuration VCS settings
  • resolved issues (\{Faradi+7.0+EAP+%2821075%29}+-\{trunk+issue}+-Task&title=TeamCity+7.0+EAP+%28build+21075%29&verbose=false)
  • No labels


  1. I have this screen for "Dependencies" in "21124", there are no "Run" buttons on pipeline steps. Does it mean there were removed?

    Update: Oh, I get it - one needs to be earlier in the pipeline to re-run the following steps. Here's a screen of the first project "Dependencies". Was this limitation intended?

    1. Well, we tried to show the buttons where they are really required. But if it's confusing, then we need a better solution.

      1. Ok, then a couple of ideas from my side:

        • Having a "Rerun" button on all pipeline steps could be better, regardless of how you came to this page: through projects in the very beginning of the pipe or the very end of it.
        • Clicking inside a step of a pipeline could bring the user to "Dependencies" tab of the corresponding project. Right now it just marks the step in yellow. However, I'm not really sure if it's useful and what's the advantage of it.
        • When the pipeline progresses it could be nice to see every step gradually filled with a color, as it happens on the front page. This will allow to visualize better the idea of water flowing through the pipe.

        This screen may provide an excellent visibility to a multi-step release process so it may become a separate screen by itself, not a part of certain project reporting tabs, hidden somewhere. It deserves to be pulled up to the very top. For example, I can think of a "Pipelines" tab next to the "Projects" on the main screen. Clicking it user will come to a dashboard of all pipelines defined in the current TC instance, being able to see how each of them progresses right now (with nice green color filling each step gradually (smile)) and, of course, being able to re-run, view log or stop each step.