![]() WARN – – Call http:://localhost:5534/RPC2 buildServer.registerAgent3: : Unexpected exception in client processing INFO – – Registering on server http:://localhost:5534, AgentDetails If yes then the first thing that you should check is the teamcity-agent.log file which is located under C:\BuildAgent\logs folder. After that, I am not able to connect the build agent from Teamcity server. I was opening up the CI (TeamCity) site to public access so I did a bit of changes in Build agent configuration and TeamCity server configuration. You can use Agent Push presets in Agent Cloud profile settings to automatically install a build agent to a started cloud instance.It seems like we have a different problem every day. ![]() You may need to download Sysinternals psexec.exe, in which case you will see the corresponding warning and a link to Administration | Tools where you can download it. The port specified in a preset can be overridden in the host name (for example, hostname.domain:2222), during the actual agent installation. Agent Push to a Linux system via SSH supports custom ports (the default is 22) specified as the SSH port parameter. In the Install agent dialog, either select a saved preset or choose " Use custom settings", specify the target host platform, and configure corresponding settings. If you want to use the same settings for several target hosts, you can create a preset with these settings and use it each time when installing an agent to another remote host. In the TeamCity UI, open Agents | Agent Push and click Install Agent. Note that to access the Agent Push page, a user needs to have the Administer build agent machines permission. Net use \\target\Admin$ /user:Administrator There are several requirements for the remote host: Make sure the "Password" or "Public key" authentication is enabled on the target host according to your preferred authentication method. Supported combinations of the server host platform and targets for build agents:įrom a Unix-based TeamCity server, build agents can be installed to Unix hosts only (via SSH).įrom a Windows-based TeamCity server, build agents can be installed to Unix (via SSH) or Windows (via psexec) hosts. TeamCity provides the Agent Push functionality that allows installing a build agent to a remote host. If you modify the state of plugins on the TeamCity server, all active agents will need to restart to synchronize with the server. Note that after starting, the full agent behaves like a regular agent. All instances will be synchronized with the server from the start and can instantly run a build. The full agent is the most convenient if you use scripts for creating agent images (for example, in cloud). This makes its distribution archive larger but significantly reduces the time spent on the first agent run. The full agent contains all enabled plugins and automatically stays relevant with the current TeamCity server state. * A minimal TeamCity agent distribution does not contain plugins: the agent downloads them on the first start. On Windows, you may want to install the build agent Windows service instead of using the manual agent startup. On Linux, you may need to give execution permissions to the bin/agent.sh shell script. Refer to this article for details on the agent configuration. Open the \conf directory and rename the file to buildAgent.properties.Įdit the buildAgent.properties file to specify the TeamCity server URL (HTTPS is recommended, see these notes) and the name of the agent. Minimal ZIP file distribution: a regular build agent with no plugins.įull ZIP file distribution*: a full build agent prepacked with all plugins currently enabled on the server.Įxtract the downloaded file into an arbitrary directory. Make sure that the JRE_HOME or JAVA_HOME environment variables are set on the agent machine and respectively point to the installed JRE or JDK directories.Ĭlick Install Build Agents and select one of the two options to download the archive: On the agent machine, run agentInstaller.exe and follow the installation instructions.Įnsure that the user account used for running the agent service has proper permissions. Preparing a container based on the official TeamCity Agent imageĬlick Install Build Agents and select Windows Installer to download the installer. ![]() ![]() Installing manually from a ZIP file on any platform Before installing a TeamCity build agent, make sure to read the system requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |