Date: Thu, 28 Mar 2024 20:01:59 +1100 (AEDT) Message-ID: <278238624.1405.1711616519474@SYDWEB02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1404_1237354484.1711616519471" ------=_Part_1404_1237354484.1711616519471 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Note that shared resources are available from version 1.8
Shared resources are used in Continua CI to restrict the number of build= s or stages accessing the same resource concurrently. This can be usef= ul if you wish to limit the number of times a particular tool is run due to= a licence or memory limit, or to prevent concurrency issues with multiple = build stages simultaneously writing to the same file, folder or network res= ource.
Each shared resource has an allocation of locks which can be acquired an= d held by builds or stages. These locks are allocated at server or age= nt level.
Server Shared Resource locks can be acquired while evaluating configurat= ion conditions and also while selecting an agent. Any builds that require S= erver Shared Resource locks, which are held by other builds, will wait on t= he build queue or stage queue until the required locks are released.
Agent Shared Resource locks are allocated per agent and can be acquired = when an agent is selected for a stage. Continua CI will chose the agent wit= h the highest available allocation of the required locks. If there are no A= gent Shared Resource locks available on any agent, the build will wait= on the 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.