No compatible agents?

I've looked through confluence and as near as I can tell, No compatible
agents means that no build agents fufilled the requirements laid out by a
particular project. However, even when the contents of requirements are
empty, I still get this message.

I thought it might have been the way in which I mucked with the
configuration, but downloading and setting up the 1075 Albus with Tomcat
gives the same problem, No compatible agents.

Any thoughts how I can get past this?

btw - I agree with many of the comments here about this being difficult to
set up. I think that's in large part because the docs are still being
written. With a reasonable set of docs, I don't imagine this would be near
as hard.

Thanks!


M


5 comments
Comment actions Permalink

As a followup, I installed the latest build and tried again. No love.
I cranked up the debugging and what I saw in the logs was mostly this.
This happens when I click to take a look at what agents are registered:

DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
WARN - dTriggers.vcs.VcsChangesLoader - Cannot load changes
jetbrains.buildServer.vcs.VcsException: Could not establish connection!
at
jetbrains.buildServer.buildTriggers.vcs.cvs.CvsCommandExecutor.executeCommand(CvsCommandExecutor.java:6)


at
jetbrains.buildServer.buildTriggers.vcs.cvs.RLogCommandExecutor.executeRLogCommand(RLogCommandExecutor.java:3)


at
jetbrains.buildServer.buildTriggers.vcs.cvs.CvsChangesProvider.collectChanges(CvsChangesProvider.java:5)


at
jetbrains.buildServer.buildTriggers.vcs.cvs.CvsSupport.collectBuildChanges(CvsSupport.java:12)


at
jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:0)


at
jetbrains.buildServer.serverSide.impl.ProjectImpl.loadChanges(ProjectImpl.java:112)


at
jetbrains.buildServer.serverSide.impl.ProjectImpl.checkForModifications(ProjectImpl.java:143)


at
jetbrains.buildServer.serverSide.impl.BuildServerImpl.checkForModifications(BuildServerImpl.java:496)


at
jetbrains.buildServer.serverSide.impl.BuildServerRunner$2.doSomething(BuildServerRunner.java)


at
jetbrains.buildServer.serverSide.impl.BuildServerRunner$BuildServerWorker.run(BuildServerRunner.java:8)


at java.lang.Thread.run(Thread.java:595)
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for
DEBUG - uildServer.web.impl.UrlMapping - Looking up
handler for


0
Comment actions Permalink

Hi Matt,

Thanks for trying Albus!
I have a couple of questions regarding your problem.

1. Do you see registered build agent on the "Agents" tab on web interface?
2. Usually, "no compatible agents" is a link which leads to the page with
explanation what's wrong with registered agents and why they cannot process builds.

You can also take a look into the files AlbusTomcat/bin/team-server.log and
AlbusTomcat/buildAgent/bin/team-server.log , this may clarify the situation a
bit.

If this won't help, please file a Jira issue at
http://www.jetbrains.net/jira/browse/TW , attach the logs and your build
configuration from $HOME/.BuildServer/config/]]>/project-config.xml

With kind regards,
KIR



Matt Ho wrote:

I've looked through confluence and as near as I can tell, No compatible
agents means that no build agents fufilled the requirements laid out by a
particular project. However, even when the contents of requirements are
empty, I still get this message.

I thought it might have been the way in which I mucked with the
configuration, but downloading and setting up the 1075 Albus with Tomcat
gives the same problem, No compatible agents.

Any thoughts how I can get past this?

btw - I agree with many of the comments here about this being difficult to
set up. I think that's in large part because the docs are still being
written. With a reasonable set of docs, I don't imagine this would be near
as hard.

Thanks!


M



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

0
Comment actions Permalink

Kirill,

Thanks for the quick response. Just to make sure I wasn't doing
something strange, I nuked the AlbusTomcat and $/.BuildServer
directories and started from scratch. Same issue.

On 2006-05-31 10:06:32 -0700, "Kirill Maximov (JetBrains)"
<Kirill.Maximov@jetbrains.com> said:

1. Do you see registered build agent on the "Agents" tab on web interface?


Yep. See the attached screenshot. When I attempt to click on the
Agents(1) link, I get the aforementioned log messages.

http://www.xtreme.com/screenshot.png

2. Usually, "no compatible agents" is a link which leads to the page
with explanation what's wrong with registered agents and why they
cannot process builds.


When I click on no compatible agents, I go to a screen that just tells
me again that I don't have a compatible agent. It's not clear why the
agent is incompatible or what needs to be done to make it happy.

Here's a screenshot of when I click on no compatible agents:

http://www.xtreme.com/screenshot2.png

M




0
Comment actions Permalink

Matt,

looks like you've got a problem with Ant runner on your build agent (see the line "Incompatible runner: Ant" on your last screenshot). Please file a Jira issue with your logs, as I described in the previous post. If there is a possible workaround, I'll let you know.

Sorry for the bug :(

KIR

0
Comment actions Permalink

Ah, figured it out. The system's iptables rules were preventing the
build agent from talking to the build server. This seems like a good
thing to include in the documentation.

M

0

Please sign in to leave a comment.