Hi there,

It seems like work is well underway on the next versions of TeamCity. I
can't find the roadmap anywhere, have you published it?

If it's not too late, I would like to give a big, big, push to
(allow failing tests to be ignored while they fail the same way).

I'm looking to add more and more system tests into TeamCity, which
typically have the property that some of them will fail consistently for
long periods. Allowing me to mark tests as "Ignored" means that
TeamCity->Red will actually mean something to our devs. At the minute,
I'm hesitating to add more tests since our welcome message for TeamCity
is "What's red and sends mail?". (OK, the e-mail thing is much better
with 3.0, thanks! But "What's red? TeamCity." isn't such a great joke.)

Why is it good for JetBrains? Well, these tests take a long time to
run, which means we will need to buy more agent licenses!


Comment actions Permalink


Thank you for the nice message :)

Actually, we are working on TeamCity 3.1 now, that is planned currently on February.
This will be a maintenance release with not a big set of features (mostly minor) included.

I will name several:
- ability to specify build working directory (directory made current before the build)
- 3 levels of clean-up (artifacts, history, statistics) instead of one
- filter by agent on build history
- quick search for builds on specific agent (@]]> syntax)
- first failure after success/success after failure notifications
- ability to watch all projects
- TLS support for e-mail sending (e.g. can use GMail as SMTP server now)
- agents load/idle time graph
- build scheduling with CRON expressions
- "time to fix" statistics
- support for NAnt 0.86
- by-module duplicates and inspections browser
- support for during-the-build artifacts publishing
- ability to report tests via special messages in stdout
- some support for proper reporting of tests running in parallel

And, of course, many fixes.

As for the next major version of TeamCity, we are still tossing ideas and determining priorities. I guess some kind of a roadmap will appear some time after 3.1.

There are lots of great ideas and (us usual) limited resources, but anyone is welcome to contribute ideas!

As for the ability to mark tests as ignored - thank you for reminding. We will try to include it into the plans, but no guarantees :)

Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
"Develop with pleasure!"

Comment actions Permalink

I'm not really sure if this is a related issue or not, but will anything be done about ANT builds that report the build will fail, even when they don't actually fail?

We have an ANT task with the failonerror attribute set to false. If this task fails it doesn't stop the build, but it does send out notification that the build will fail, even though the error should be ignored. The build will then complete successfully, but not send out notification of success.

Comment actions Permalink


3.1 will have an option tweaking TeamCity's understanding of a failing build and this should eliminate the issue.

A current workaround is to configure notification not to receive "Notify when the first error occurs" notifications. (or add "The build is successful" notification if you want to be notified on successful builds)

Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
"Develop with pleasure!"

Comment actions Permalink

Great. Thanks for the quick response!


Please sign in to leave a comment.