We have a VSTS on a server which has around 4 agents. When this task logs in to CF it uses the location "/.cf/config.json" as a semaphore to persist the session. If I login from an agent and start the release and parallelly if another release is going on, they both touch the same semaphore and results in conflict.
We have a VSTS on a server which has around 4 agents. When this task logs in to CF it uses the location "/.cf/config.json" as a semaphore to persist the session. If I login from an agent and start the release and parallelly if another release is going on, they both touch the same semaphore and results in conflict.