[Fwd: Public Team Server]


-


Original Message -


Subject: Public Team Server
Date: Thu, 23 Mar 2006 18:23:59 +0300
From: Kirill Maximov (JetBrains) <Kirill.Maximov@jetbrains.com>
Organization: Jetbrains, Inc.
Newsgroups: jetbrains.teamware.eap

Hi,

We've opened a public Team Server to show you what it looks like
without need to download/install the thing. Take a look here:

http://teamserver.jetbrains.com

Please, do not install your own build agents - we are not ready to
this yet :). And they won't work.

Kind regards,
KIR

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

4 comments

We've opened a public Team Server to show you what it looks like
without need to download/install the thing. Take a look here:

http://teamserver.jetbrains.com

Nice, but very slow :).
Maybe you should not use SpringMVC as framework for the Teamserver , but
something faster :).

Ahmed.

0

Ahmed Mohombe wrote:
>> We've opened a public Team Server to show you what it looks like
>> without need to download/install the thing. Take a look here:
>>
>> http://teamserver.jetbrains.com

Nice, but very slow :).
Maybe you should not use SpringMVC as framework for the Teamserver , but
something faster :).


Probably the server is slow not because of SpringMVC but because of
networking issues. Locally it works pretty fast.

Is it very slow for everyone?

Regards,
KIR


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

0

>>> We've opened a public Team Server to show you what it looks like
>>> without need to download/install the thing. Take a look here:
>>>
>>> http://teamserver.jetbrains.com

great - since I still haven't had time to install it yet


>> Nice, but very slow :).
>> Maybe you should not use SpringMVC as framework for the Teamserver , but
>> something faster :).


Probably the server is slow not because of SpringMVC but because of
networking issues. Locally it works pretty fast.

Is it very slow for everyone?


no, at least UI access is pretty fast, I can't comment about build
speeds ;) of course

I like the usability just a couple of comment so far:

a) I think the overview tab will become crowded quickly. we're
currently using damagecontrol with about 30 projects on the build
server and it looks cramped already with a one line status per project.
So provide a dashboard view with (collapsed) projects or perhaps even
better a build matrix.

b) I suppose there will be an API and UI for scheduling builds?

c) what are Artefacts? build input or build output? (it looks like
input as the "Ant" build as artefacts although it fails)... if so, it
would be nice to be able to collect/archive/publish the build output
artifacts if the build was successful

d) provide a public and a private view, ie. separate a view that only
displays build health and vital signs (without any option to change
configuration or trigger builds) for managers and other non-tech staff,
from the developer/build master view



O

0

Please sign in to leave a comment.