TCP Agent configuration

[sergio.gonzalez_0157]

Hello everyone,

I've been asigned with managing an existing buildmaster server and I'm having quite some trouble configuring the deployment workflow.
Here's a brief summary of my situation:

• I have my Server: ProductionServer, Inedo Agent (v46, ProductionServer:1001); Status: Ready; Agent: Inedo; Environments: Development, Testing, Acceptance, Clone; Roles: JumpServer
• My new Server: ProductionServer2, Inedo Agent (v51, ProductionServer2:1001); Status: Ready; Agent: Inedo; Environments: Clone; Roles: JumpServer2
• In addition I also have a local BuildMaster Server, bmx::local; Status: Ready; Agent: Local, Environments: none; Roles: none
• My deployment script is something like this:

        for server BuildMaster Server
        {
            InedoCore::Exec
            (
                FileName: C:\Tools\HolyDevCli\HolyDevCli.exe,
                ...
            );
        }

• However, when I check the execution logs, here's what I get:

DEBUG: 2024-01-30 14:53:49Z - Using LocalAgent agent on BuildMaster Server
DEBUG: 2024-01-30 14:53:49Z - Process: C:\Tools\HolyDevCli\HolyDevCli.exe
...
INFO : 2024-01-30 14:53:49Z - Executing C:\Tools\HolyDevCli\HolyDevCli.exe...
INFO : 2024-01-30 14:53:50Z - Busy
INFO : 2024-01-30 14:53:50Z - Process exited with code: 0 (success)
DEBUG: 2024-01-30 14:53:50Z - Using TcpAgent agent on ProductionServer

And I have no idea where or how it is set the destination server to be "ProductionServer"

I'm running Version 6.2.14 (Build 17)

Any help or new idea would be greatly appreciated.
Many thanks in advance

[dean-houston]

Hi @sergio-gonzalez_0157 ,

Typically, Deployment Targeting is done in the Pipeline:
https://docs.inedo.com/docs/buildmaster/deployment-continuous-delivery/buildmaster-pipelines#deployment-targets

This way, you don't need to put for server or anything in your script.

So, my guess is that your Pipeline is actually targeting the ProductionServer (but not running anything on it, except intializing the agent), but your script is targeting the BuildMasterServer.

-- Dean