BuildForge Agent/Engine compatibility question

The best answer for your situation would be to incrementally upgrade some of the agents in the farm and make it easy for yourself to exclude them from the build pool if necessary.  Then just test the newer agents with your current builds and see how it goes.  There PROBABLY won't be any issue, since any newer functionality in the agent will just not be used by the 7.0.2 console, but that use case is really just best effort on our part.  We cannot guarantee it will work, but we try hard to allow it to work.  Its roughly equivalent to deprecating a method.  We want to allow you to continue using it, but its really at your own risk.

Hello,

This is known as Agent Interoperability. I think I spelled that right. . The ability of the agent to work with various versions of the console working with various versions of the agent.

7.0.2 agent should work with 7.1.3.5. Keep in mind 7.1.3.5 has better functionality an additional features. These changes hve also caused the agent to have to changes including defect fixes as well.

Now, to have 7.0.2 instance running 7.1.3.5 agent. This cold work for somet things, but we do see a lot of issues with this and I would not recommend it.

FIX:

The best thing to do is install a 7.1.3.5 agent on your target machine WITH a 7.0;.2 agent. Just have one agent the 7.1.3.5 agent using the default 5555 port and the other agent using something different. Say 7777.  This would allow you to have two agents on one machine. They will both be able to connect to there designed Build Forg Consoles.

There is also more information in the info center under Agent Interoperability.

Hope this helps.

Thanks!

Hello,

Yeah, I have no reason to believe that this would not work. As long as the two agents do not share a port number, you shoul be good to go.

Let us know if you have any issues or additional concerns.

Thannks!