build agent on a different machine

Although it is possible to install both on the same machine, the server is likely to become unresponsive because the agent may
consume much memory and CPU resources (depending on the build being executed).

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

"bin zhu" <no_replay@jetbrains.com> wrote in message news:16486480.1142350622404.JavaMail.itn@is.intellij.net...

just curious. why does the faq say:

>

"It's not recommended to install the agent and the server on the same computer."

>

by the way, great start on the TeamWare project!

>

thanks,

i was hoping for a default build agent on the server

what if the project specifies build agent performance/hardware requirements, and the default build agent on the server has low threasholds so that it can still build smaller projects?

also.. i guess that right now we can only manually install agents on headless/browserless servers

what if the project specifies build agent performance/hardware requirements, and the default build agent on the server has low
threasholds so that it can still build smaller projects?

I think for small projects both server and agent on the same machine are ok.

also.. i guess that right now we can only manually install agents on headless/browserless servers

Yep

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

Although it is possible to install both on the same
machine, the server is likely to become unresponsive
because the agent may
consume much memory and CPU resources (depending on
the build being executed).

How about a way to specify a build agent niceness?

How about a way to specify a build agent niceness?

Well, we can do it, but will this really help?

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

IMHO it is very important to be able to have both on the same machine.
Here's an example:
I was very eager to try the team features of Demetra, so I was thrilled
when I read about the EAP release.
Well, I proceeded as far as to read the notes about needing separate servers.
I may have one machine to spare, but if I need two machines and two separate
installs - I may better get back to my real work and make some progress on
my current project.

I think the default install should install both the server and one agent on
the same machine and you should try and take care of any resource conflicts
that might arise (using niceness, better scheduling whatever).

You can of course add a recommendation in big, bold letters that for larger
projects the agent should be on a separate machine...


Eugene Zhuravlev (JetBrains) wrote:
>> How about a way to specify a build agent niceness?

Well, we can do it, but will this really help?

Stephen Kelvin wrote:

IMHO it is very important to be able to have both on the same machine.

You can do it. No great problem here for small and medium size
projects. And we do it daily in development environment (in fact,
sometimes my comp runs team server under debug from IDEA, build agent,
and build agent is building teamserver itself while I'm working in IDEA)

But if you'd like to get faster feedback about your commits and want to
have less changelists going to a single build, more agents are better.

Here in JetBrains we have 10 build agents, which run Demetra, 5.1, Team
Server, Resharper builds. And sometimes all of them are busy.

Here's an example:
I was very eager to try the team features of Demetra, so I was thrilled
when I read about the EAP release.
Well, I proceeded as far as to read the notes about needing separate
servers.
I may have one machine to spare, but if I need two machines and two
separate
installs - I may better get back to my real work and make some progress on
my current project.

I think the default install should install both the server and one agent on
the same machine and you should try and take care of any resource conflicts
that might arise (using niceness, better scheduling whatever).

You can of course add a recommendation in big, bold letters that for larger
projects the agent should be on a separate machine...

OK, we've removed boldness :)

Eugene Zhuravlev (JetBrains) wrote:

>>> How about a way to specify a build agent niceness?
>>
>> Well, we can do it, but will this really help?
>>


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