Hello,
I've been running in trouble recently with Bamboo, when changing the way it is started on the agents. Previously, all OS X agents on Bamboo were starting using a script as a login item. Now that the agents are being migrated to being set up using Ansible, we can't do that anymore (thanks to security on Mojave), so we moved towards using a user Launch Agent for that, as recommended in the Bamboo documentation.
It brings some nice stuff, like the agent reloading Bamboo automatically when it stops for some reason, but also causes trouble: whenever we reboot the machine, and Bamboo starts again, the server will give it a new unique name (the initially configured name, with '(2)' at the end), and also a new ID, as it seems the server is still seeing the 'old' agent. It's still the same machine, with the same domain name and IP.
On the server side, this also means that the "new" agent has no capabilities, and thus won't build much. The only solution then is to request a shutdown, rename on both the agent and on the Bamboo server, and also re-enter the right ID on the agent. Quite cumbersome...
Tried looking at the logs both on the agent and the server, but not much there to be seen so far...
Any idea what could cause this and how to avoid it?
