Can the RTC server list JBE hostnames?
What is the best way to see the hosts connected to RTC as jazz build engines and what user id they are connected as?
I have a problem where lots of jazz build engines have been created in RTC on lots of different machines and connected using a single task id, when it comes to the time to change the password for this task id I can't find any way of listing the machines connected to RTC using that task id so I need to maintain a list of the JBE names, the host they are running on and the username they connect with, is there anyway of getting this information from RTC in logs or through the API? It is particularly problematic as the manually created list gets out of date or machines missed through human error, so it would be very useful to be able to query this from the RTC server.
A related problem, we have all these machines running JBEs when we want new machines to do a similar job we just clone the machine, however this results in the name the JBE is started with being the same on both machines which RTC doesn't allow. As we don't control the cloning of machines it is hard for us to know when a new clone will be created and more importantly which machine is created with a JBE matching name, breaking our existing working builds. E.g
Host host01 running JBE jbe05
Cloned to :
Host host07 running JBE jbe05
The JBE jbe05 won't work because it is running on 2 machines, but it seems impossible to tell where the 2 conflicting JBEs are running, can you offer any suggestions?
One answer
Comments
But if I attempt to start another instance of BE5 (for example) it will fail long before logging a job.
Why? That seems like a different issue than what Alix is reporting.
Builds that do get started will log the host name. I think the issue with JBE running on multiple hosts for the same engine id is that it will auto-abandon builds, thinking that they've been orphaned (i.e. it's not the current JBE running them, so it abandons them).
You can disable the auto-abandon behaviour with:
jbe ...regular args… -vmargs -Dteam.build.abandonOrphans=false
It would certainly help to have the auto-abandon log message to also include the host name, would this tell you both hostnames or just one of them?
There is a third problem case in there area, what if a person creates a JBE on a build machine but doesn't create a build engine in the RTC server, is there anyway to find out if such a JBE exists from the RTC server?
> It would certainly help to have the auto-abandon log message to also include the host name
> what if a person creates a JBE on a build machine but doesn't create a build engine in the RTC server
huh? if I create a new JBE build process on some server using some ID which does not exist, then the jbe command reports
[Jazz build engine] CRRTC3521W: Warning: The build engine is
either not in the repository, or it cannot be accessed by the following user: "sam". The ID of the build engine is "test on 5 engine1".
Comments
sam detweiler
May 14 '14, 6:28 a.m.There is really no linkage between JBE build engine ID and the machine hostname.