Child pages
  • Gaya 8.0 EAP (build 26984) Release Notes
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

VCS worker (experimental)

VCS worker is a part of TeamCity server responsible for communication with VCS repositories. This is a separate Java process which can be installed on any machine in your network. TeamCity server can be configured to use one or more VCS workers. In this case all VCS specific tasks will be routed to appropriate workers. For example, it is possible to route all Git specific requests to one worker, and Subversion requests to another.

By default VCS worker is disabled, and TeamCity behaves as usual, i.e. performs all VCS operations from the main server process.

With large setups VCS worker(s) installed on separate machine should decrease TeamCity server load significantly. Please refer to our documentation for instructions how to configure TeamCity in conjunction with VCS worker:

Project groups

Ability to create sub-projects, move project under another project, parameters inheritance.

Server health reports

New page was added in Administration area: Server health. Our intention is to provide server administrators with different reports highlighting possible configuration problems. Currently the following reports are available:

  • Database related problems
  • Redundant VCS roots, i.e. VCS root duplicates
  • Unused VCS roots
  • VCS settings increasing the probability of clean checkout
  • Critical errors in configuration files
  • and others

Disk usage report

Have you ever tried to figure out which project artifacts ate most of disk space on the server? If yes, then you'll appreciate this feature. It shows you the size of artifacts and build logs in each project and configuration, and allows to find hot spots easily.

Queued build page

Build queue is a kind of shadow world of TeamCity. While build stays in queue there is no easy way to overview its parameters, changes, dependencies and so on. Internally, queued build does not differ much from regular build, so we thought it would be good to show it details in almost the same way. Now in build queue you can click on the #number link and you'll be redirected to the queued build page with all familiar tabs:

  • Changes
  • Parameters
  • Dependencies
  • Compatible agents

Our plan is to improve dependencies presentation on this page, to simplify discovering of the current build chain state and progress.

Sub-repositories support for Git & Mercurial

  • No labels