Channels ▼


JetBrains Announces TeamCity 7.0

JetBrains has announced TeamCity 7.0 with an eye on wooing developers who seek productivity-enhancing tools to support distributed build management and continuous integration (CI) processes.

The new version release has been built with additional provision for incremental builds and unit testing (specifically suited for Maven, Gradle, and IntelliJ IDEA projects) and there is also support for extended build chains and visualization.

The JetBrains team says it has addressed build failure conditions with renewed empathy and concern; it has also brought in branch graphs to illustrate change history (in Git and Mercurial) and now uses TeamCity as a native NuGet feed server.

"TeamCity is many different things to many types of companies and users. To meet their diverse needs, we took a closer look at various user experiences and tried to improve them all around," said Pavel Sher, TeamCity project lead. "To further facilitate complex build workflows, we've added build chain visualization, typed parameters and powerful build failure conditions. Our customers with a large number of agents will benefit from more predictable agents distribution among projects. As always, there are many usability enhancements for all users."

NOTE: TeamCity is a continuous integration server for developers and build engineers. It is free for small teams.

JetBrains is fond of quoting enterprise software evangelist Martin Fowler for a convenient definition of continuous integration. Fowler's classification in full does make enjoyable reading:

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily — leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.