Sashka's Weblog

I am not a jensen harris, but our public version of Team Server gets updated not as quickly as we develop new features, so I am going to write a bit about what we are doing.

Recently we've re-designed the Results view, one of the most important pages of our Team Server (because software developers need to understand the reasons behind a build failure).

Now all essential information can be found on just one page:

- which tests have failed,
- whether there're any new failing tests
- when the tests start to fail (if it's not the first time)
- who has committed the changes that led to the failure

You can click on a failed test name and get full stacktrace text (in the future you'll be able to click and open it in your IDE):

Hover over the Changes link new the test name and you'll see who has commited the change, comment he wrote for this changelist and the number of changed files.

I hope we'll have it on the public server in a couple of days, so you can see who it works. And if you want to try it on your own project, we have an open Early Access Program.

Posted by Sashka at 7:38 PM | Permalink

I am not sure it is any news to the most of my readers, but in case it is, I will explain my silence :) I've got a new job.

About four weeks ago I switched from the JB corporate web-site development and management to the user interface design and development of a new product. The tool is called (so far) Team Server and, as you can easily conclude, it serves the nasty task of running builds, detecting problems, and reporting them to the team of developers.

Those who happend to roam through the office seeking for blood after someone's ruined a build and went home, will immediately understand the benefits:

- Team Server can run many builds for many different projects simultaneously.
- It has one single user interface where you can get an overview of what's being run on different agents.
- It shows history for each build type - changes, time, duration, etc, etc.
- It shows stacktraces (which a couple of iterations later you'll be able to click and open in IntelliJ IDEA).
- It sends notifications as soon as a problem is detected, so you don't have to wait till the build process is completed.
What I've forgot to mention?
Well, the user interface is far, far, faaar from completion. It is "under development" and will be for several months more. We are trying out all those AJAX-smajax fashion tricks, changing layouts, fonts and colors, supporting new features, etc.

And isn't it the right time to download Team Server and tell us what you think in news://news.jetbrains.com/jetbrains.teamware.eap?

Posted by Sashka at 3:31 PM | Permalink