Wish list

I haven't played with the server yet, just looked at the demo server... And here is my wish list..

  • It would be nice if every user could select the projects to look at (and/or the administrator could configure that). That is because the same build server is often used to build many projects but developers have little interest in other projects - they just clutter the screen

  • Does the build server detect individual changelists for VCS that support that? (SVN, Perforce)? Sometimes >1 change is done within check interval and the build server just builds all them together. My homegrown build server detects individual changes and builds them separately. It's strange why tools like CC dont' support that, it is quite useful.

Also, the history should contain VCS change number, it's much easier to refer to than time.

  • Is it possible to execute custom (non-junit) tests during the build and somehow publish the stats (like # integration test passed, failed, etc) to the front page?

  • Would it be possible to perform "diif" between test result, to display "tests that were broken/fixed in this change?"

3 comments
Comment actions Permalink

Hello Igor,

Igor Karpov wrote:

I haven't played with the server yet, just looked at the demo server... And here is my wish list..

  • It would be nice if every user could select the projects to look at (and/or the administrator could configure that). That is because the same build server is often used to build many projects but developers have little interest in other projects - they just clutter the screen


Please vote/comment request
http://www.jetbrains.net/jira/browse/TW-28

  • Does the build server detect individual changelists for VCS that support that? (SVN, Perforce)? Sometimes >1 change is done within check interval and the build server just builds all them together. My homegrown build server detects individual changes and builds them separately. It's strange why tools like CC dont' support that, it is quite useful.

Also, the history should contain VCS change number, it's much easier to refer to than time.


It doesn't so far. There will be another related feature - remote
run, which allows to run your changelist on the server without
commiting to VCS. If this is not enough and you think that individual
change detection in VCS is mandatory, please file a request for that.

  • Is it possible to execute custom (non-junit) tests during the build and somehow publish the stats (like # integration test passed, failed, etc) to the front page?


No, at least out of the box. Currently, to pass test information to
the server, a specific Ant listener is used, which is bound to Ant's
junit task. To send information from another test runner, another
extension should be written.

  • Would it be possible to perform "diif" between test result, to display "tests that were broken/fixed in this change?"


So far you can distinguish new/old failing tests in the failed build.
And in the old builds, you'll be able to see already fixed tests
(see/vote for http://www.jetbrains.net/jira/browse/TW-199).


Thank you very much for your feedback!
Kind regards,
KIR


--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

>It doesn't so far. There will be another related feature - remote
run, which allows to run your changelist on the server without
commiting to VCS. If this is not enough and you think that individual
change detection in VCS is mandatory, please file a request for that.

I meant that it's just much more convenient to have VCS change numbers in history, that is for commited changes. To run changes on server without commiting is also very nice but different feature.

>

  • Is it possible to execute custom (non-junit) tests during the build and somehow publish the stats (like # integration test passed, failed, etc) to the front page?


No, at least out of the box. Currently, to pass test information to
the server, a specific Ant listener is used, which is bound to Ant's
junit task. To send information from another test runner, another
extension should be written.

- Is is possible to have some docs how it can be done? I mean where to configure this listener?

0
Comment actions Permalink

I meant that it's just much more convenient to have
VCS change numbers in history, that is for commited
changes. To run changes on server without commiting


I've created a request for this:
http://www.jetbrains.net/jira/browse/TW-216


No, at least out of the box. Currently, to pass test
information to
the server, a specific Ant listener is used, which is
bound to Ant's
junit task. To send information from another test
runner, another
extension should be written.

- Is is possible to have some docs how it can be
done? I mean where to configure this listener?


Could you possibly describe your task more precisely?
Currently, it is pretty difficult task to implement own test
message logger, and we're doing many changes in this
area. Current implementation in EAP works only with junit
task.

With kind regards,
KIR

0

Please sign in to leave a comment.