Team Server build 909 EAP

How is the plugin functionality accessed. I can login, but then all I get is a green button on the toolbar?

--Dave Griffith

Firstly, fill your profile on the team server, including VCS names and jabber account for notifications.

Secondly, setup your project in the team server (unfortunately, this requires manual editing of the config files, see FAQ of the team server for details).

Then, make sure that IDEtalk in IDEA connected to your jabber account (the icon at the bottom of the IDEtalk toolwindow should be green, if not, press it and specify jabber parameters)

After that, you can make a remote run of your changes from IDEA: in changes toolwindow, select a changelist to be run on the team server, and invoke Remote Run command (currently it has debugger icon). In the 'commit' dialog, choose run configurations which should be used to build your changes. If everything is done correctly, you'll be notified when remote build is started/failing/completed. Clicking on the icons in toolbar should invoke a list of commands regarding your commits: left icon - commits to VCS, right one - about personal build.

Hope this helps,
Kind regards,
KIR

Wow, that's complicated. I actually had done the first three of those, and loved what I saw. The fourth I never would have figured out, as I only use the "Changes" window when I've let things go too long between check-ins. Otherwise "Commit Project" is enough. There needs to be some easier and clearer way trigger remote runs (like a menu item under the "Build" main menu) and some less intrusive way to indicate that a project is using the build server (like a config panel).

A+ for functionality, C for usability, at least so far. Fortunately the "remote build" functionality alone is more than enough to make the sale for me.

--Dave Griffith

Firstly, fill your profile on the team server, ....

From a functionality point of view it's just impressive, but IMHO for usage, it's just too
complicated(reminds me of MPS :) ).

IMHO you should totally simplify(and rethink) the workflow(and add some wizards): the average Joe
programmer won't be able to use it or will abandon pretty quickly.

just my 2 cents,

Ahmed.

IMHO you should totally simplify(and rethink) the
workflow(and add some wizards): the average Joe
programmer won't be able to use it or will abandon
pretty quickly.

Completely agree here. I was thinking just like that while
writing my previous post. The process of setting up the remote run
is too much complicated. What we're thinking of:

- remove dependency on Jabber/IDEtalk to get personal build notifications
- automatically detect team server run configurations which should be run
remotely according to VCS roots in the changelist
- provide the Remote Run command in the Ctrl-K dialog.
- improve build data presentation in some way (popup window
which appears after the click on the toolbar button)

May be anything else?

With kind regards
KIR

>> IMHO you should totally simplify(and rethink) the
>> workflow(and add some wizards): the average Joe
>> programmer won't be able to use it or will abandon
>> pretty quickly.

Completely agree here. I was thinking just like that while
writing my previous post. The process of setting up the remote run
is too much complicated. What we're thinking of:

- remove dependency on Jabber/IDEtalk to get personal build notifications
- automatically detect team server run configurations which should be run
remotely according to VCS roots in the changelist
- provide the Remote Run command in the Ctrl-K dialog.
- improve build data presentation in some way (popup window
which appears after the click on the toolbar button)

That sounds good. I can't wait to try them :).

May be anything else?

Well, I would say: wizards. While I know that the wizards are not important in an IDE for the
current work(coding), but for setting up things,IMHO it is very important to have simple to use
wizards - they require no previous knowledge or long learning periods.

Also it might make sense to make more use of defaults/defaulting. Things that fit for most of
the people in a certain usage scenario, should already be configured or filled.

Ahmed.

Remote Run on Ctrl-K would be just fine. I assume "Deferred Commit" means something like "Remote Run and then check-in if everything passed", and that should go as another flag on the Ctrl-K panel.

I'll also suggest again that a menu button under "Version Control" to pop up the Changes toolwindow would be very handy, and make Changes vastly more likely to be used.

--Dave Griffith

There needs to be some easier and clearer way trigger remote runs

Try to click on 'Remote Build User Status' action in the main menu (in
IDEA). There is the list of all remote runs with the possibility to remote
some finished ones. Did you test it?

"Dave Griffith" <dave.griffith@cnn.com> wrote in message
news:31129701.1145106193689.JavaMail.itn@is.intellij.net...

Wow, that's complicated. I actually had done the first three of those,
and loved what I saw. The fourth I never would have figured out, as I
only use the "Changes" window when I've let things go too long between
check-ins. Otherwise "Commit Project" is enough. There needs to be some
easier and clearer way trigger remote runs (like a menu item under the
"Build" main menu) and some less intrusive way to indicate that a project
is using the build server (like a config panel).

>

A+ for functionality, C for usability, at least so far. Fortunately the
"remote build" functionality alone is more than enough to make the sale
for me.

>

--Dave Griffith

+Try to click on 'Remote Build User Status' action in the main menu (in
IDEA). There is the list of all remote runs with the possibility to remote
some finished ones. Did you test it?+

Yup, just tried it. Same verdict: A+ for functionality, C for usability. Difficult to configure, and extends the IDEA UI in non-standard and confusing ways, but once you get it figured out the actual functionality rules mightily.

--Dave Griffith