Shared Resources are used in Continua CI to limit the number of builds or stages from certain configurations which can run concurrently on the server or an agent. Each shared resource has an allocation of locks which can be acquired and held by Builds or Stages. This This can be useful if you wish to limit the number of times a particular tool is run due to a license or memory limit, or to prevent concurrency issues with multiple build stages simultaneously writing to the same file, folder or network resource.
Each shared resource has an allocation of locks which can be acquired and held by builds or stages. This Shared Resource locks are allocated at server or agent or server level.
Server Shared Resource locks can be acquired while evaluating configuration conditions and also while selecting an agent. Any builds which require Server Shared Resource locks which are held by other builds will wait on the build queue or stage queue until the required locks are released.
...
Shared Resource locks are automatically released at the end of the build or stage which acquired the lock.
Types of Shared Resource
Single: A single read or write lock. Only one build or stage can acquire a lock on this Shared Resource at any time. This is useful if build actions require exclusive access to a resource on a server or agent
...